Sensor-based interruption of an irrigation controller

ABSTRACT

Some embodiments provide a system and method for interfacing with an irrigation controller based on rainfall, the system comprising: an interface unit including a housing and a control unit within the housing and configured to: cause an interruption of one or more watering schedules executed by the irrigation controller, which is separate from the interface unit, based on signaling received from a rain sensor including hygroscopic material, when a sensed expansion of the hygroscopic material is above a set rainfall accumulation threshold parameter, the rain sensor being separate from the interface unit and the hygroscopic material being configured to expand in response to being contacted by the rainfall and to contract in response to an absence of the rainfall; and remove the interruption after a completion of a predetermined interval of time after a sensed contraction of the hygroscopic material indicative of a rainfall stop.

This application is a continuation of U.S. application Ser. No.16/933,182, filed Jul. 20, 2020, which is a continuation of U.S.application Ser. No. 15/791,160, filed Oct. 23, 2017, now U.S. Pat. No.10,757,873.

This application is related to the following applications, all of whichare incorporated in their entirety herein by reference: U.S. applicationSer. No. 15/495,726, filed Apr. 24, 2017, now U.S. Pat. No. 10,444,769;U.S. application Ser. No. 14/830,600 filed Aug. 19, 2015 now U.S. Pat.No. 10,206,342; U.S. application Ser. No. 13/277,224 filed Oct. 20,2011, now U.S. Pat. No. 9,144,204; U.S. application Ser. No. 13/113,900filed May 23, 2011; U.S. application Ser. No. 13/151,269 filed Jun. 1,2011; U.S. application Ser. No. 11/766,092 filed Jun. 20, 2007, now U.S.Pat. No. 7,949,433; U.S. application Ser. No. 13/479,111 filed May 23,2012, now U.S. Pat. No. 8,733,165; U.S. application Ser. No. 14/253,716filed Apr. 15, 2014, now U.S. Pat. No. 9,500,770; and U.S. applicationSer. No. 15/331,565 filed Oct. 21, 2016, now U.S. Pat. No. 9,500,770.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates generally to the controlling of theexecution of a watering program by an irrigation controller.

2. Discussion of the Related Art

Rain sensors for use in the interruption of programmed wateringschedules of an irrigation controller are generally known to include amaterial that is responsive to rain, and in the event a preset level ofrain is exceeded, a switch is activated which outputs a signal to theirrigation controller that causes the controller to cease the executionof watering schedules.

U.S. Pat. No. 6,452,499 to Runge et al. (which is incorporated herein byreference) describes a wireless rain sensor that uses a hygroscopicmaterial that expands when exposed to water. When the hygroscopicmaterial expands beyond a specified point or threshold, an integratedtransmitter wirelessly transmits a radio frequency signal to a receiverattached to the controller. The receiver receives the wireless signaland causes the controller to cease watering. Similarly, U.S. Pat. No.6,977,351 to Woytowitz (which is incorporated herein by reference)describes a wireless rain sensor including a hygroscopic material thatis not mechanically connected to the switch that triggers thetransmission of the wireless signal that will cause the interruption ofwatering The threshold level may be adjusted by a user through themechanical adjustment of the distance the hygroscopic material mustexpand before actuating the switch, such as described in U.S. Pat. No.6,570,109 to Klinefelter et al (which is incorporated herein byreference). Thus, in order to exceed a selectable threshold, thehygroscopic material must expand a selectable distance, whichcorresponds to a selectable level of rain fall.

SUMMARY OF THE INVENTION

Several embodiments of the invention advantageously address the needsabove as well as other needs by providing a system for interfacing withan irrigation controller based on rainfall comprising: an interface unitincluding a housing and a control unit within the housing and configuredto: cause an interruption of one or more watering schedules executed bythe irrigation controller, which is separate from the interface unit,based on signaling received from a rain sensor including hygroscopicmaterial, when a sensed expansion of the hygroscopic material is above aset rainfall accumulation threshold parameter, the rain sensor beingseparate from the interface unit and the hygroscopic material beingconfigured to expand in response to being contacted by the rainfall andto contract in response to an absence of the rainfall; and remove theinterruption after a completion of a predetermined interval of timeafter a sensed contraction of the hygroscopic material indicative of arainfall stop.

Further, in some embodiments, a method for interfacing with anirrigation controller based on rainfall comprises: providing aninterface unit including a housing and a control unit within thehousing; causing, via the control unit, an interruption of one or morewatering schedules executed by the irrigation controller, which isseparate from the interface unit, based on signaling received from arain sensor including hygroscopic material, when a sensed expansion ofthe hygroscopic material is above a set rainfall accumulation thresholdparameter, the rain sensor being separate from the interface unit andthe hygroscopic material being configured to expand in response to beingcontacted by the rainfall and to contract in response to an absence ofthe rainfall; and removing, via the control unit, the interruption aftera completion of a predetermined interval of time after a sensedcontraction of the hygroscopic material indicative of a rainfall stop.

In addition, some embodiments provide an interface unit interfacing withan irrigation controller, the interface unit comprising: a housing; acontroller within the housing, where the controller is configured inpart to determine whether an interruption of one or more wateringschedules executed by the irrigation controller, which is separate fromthe interface unit, should occur and to output signaling to instruct theinterruption, the interruption based at least on a sensed rainfallaccumulation amount and a user set rainfall threshold parameter; aswitching device coupled with the controller, and configured to causethe interruption in response to the signaling from the controller; and auser interface integrated with the housing and comprising: a pluralityof user input devices coupled to the controller and configured toprovide signaling to the controller based upon a user's engagementtherewith, the plurality of user input devices configured to allow theuser to set and adjust at least the user set rainfall thresholdparameter; and a user display comprising a display screen and coupled tothe controller and configured to display one or more pictorialrepresentations; wherein the controller is configured to cause thedisplay screen to display a plurality of pictorial representations thatin combination convey to the user the sensed rainfall accumulationamount, the user set rainfall threshold parameter and whether irrigationis being interrupted.

Some embodiments can be characterized as methods for use in irrigationcontrol, comprising: receiving a user set and adjustable rainfallthreshold at a user interface integrated with an interface device, theinterface device configured to cause interruption of one or morewatering schedules executed by a separate irrigation controller;receiving at the interface device, from a remote sensor unit, sensedrainfall information; and displaying, at the interface device, multiplepictorial representations corresponding to the sensed rainfallinformation and the user set and adjustable rainfall threshold such thata state of interrupting irrigation based at least on a relationshipbetween the sensed rainfall information and the user set and adjustablerainfall threshold is conveyed.

Further, some embodiments provide an interface unit interfacing with anirrigation controller, the interface unit comprising: a housing; acontroller within the housing, where the controller is configured inpart to determine whether an interruption of one or more wateringschedules executed by the irrigation controller, which is separate fromthe interface unit, should occur and to output signaling to instruct theinterruption, the interruption based at least on a sensed rainfallaccumulation amount and a user set rainfall threshold parameter; aswitching device coupled with the controller, and configured to causethe interruption in response to the signaling from the controller; and auser interface integrated with the housing and comprising: a pluralityof user input devices coupled to the controller and configured toprovide signaling to the controller based upon a user's engagementtherewith, the plurality of user input devices configured to allow theuser to set and adjust at least the user set rainfall thresholdparameter; and a user display comprising a display screen and coupled tothe controller and configured to display one or more pictorialrepresentations; wherein the controller is configured to cause thedisplay screen to display a plurality of pictorial representations thatin combination convey to the user a mode of operation and whetherirrigation is being interrupted.

Additionally, some embodiments provide a method used in controllingirrigation, comprising: receiving, through a user interface of aninterface unit, a user set and adjustable rainfall threshold parameter,the interface unit configured to interrupt one or more wateringschedules executed by an irrigation controller, which is separate fromthe interface unit; receiving, at the interface unit and from a sensorunit that is separate from the interface unit, a sensed rainfallaccumulation amount; and displaying, on a display of the interface unit,multiple pictorial representations that in combination convey to a usera mode of operation and whether irrigation is being interrupted based atleast on a relationship between the user set and adjustable rainfallthreshold parameter and the sensed rainfall accumulation amount.

Furthermore, some embodiments provide a system for controllingirrigation based on rainfall. The system comprise an irrigationcontroller configured to execute one or more watering schedules and aserver remote to a location where the irrigation controller isinstalled. The server is in communication with the irrigation controllerover a network and includes a control unit configured to: obtain weatherdata associated with the location where the irrigation controller isinstalled; cause an interruption of one or more watering schedulesexecuted by the irrigation controller in response to receipt by theserver of weather data indicative of active rainfall in the locationwhere the irrigation controller is installed; and remove theinterruption after a completion of a predetermined interval of time inresponse to receipt by the server of weather data indicative of arainfall stop in the location where the irrigation controller isinstalled.

In some additional embodiments, a method for controlling irrigationbased on rainfall comprises: providing an irrigation controllerconfigured to execute one or more watering schedules; providing a serverremote to a location where the irrigation controller is installed, theserver being in communication with the irrigation controller over anetwork and including a control unit; obtaining, via the control unit,weather data associated with the location where the irrigationcontroller is installed; causing, via the control unit, an interruptionof one or more watering schedules executed by the irrigation controllerin response to receipt by the server of weather data indicative ofactive rainfall in the location where the irrigation controller isinstalled; and removing, via the control unit, the interruption after acompletion of a predetermined interval of time in response to receipt bythe server of weather data indicative of a rainfall stop in the locationwhere the irrigation controller is installed.

Some additional embodiments provide a system for controlling irrigationbased on rainfall. The system comprises an irrigation controllerconfigured to execute one or more watering schedules and a server remoteto a location where the irrigation controller is installed. The serveris n communication with the irrigation controller over a network. Theirrigation controller is configured to obtain, from the server and overthe network, weather data associated with the location where theirrigation controller is installed. The irrigation controller includes acontrol unit configured to: cause an interruption of one or morewatering schedules executed by the irrigation controller in response toreceipt, by the irrigation controller from the server, of weather dataindicative of active rainfall in the location where the irrigationcontroller is installed and remove the interruption after a completionof a predetermined interval of time in response to receipt, by theirrigation controller from server, of weather data indicative of arainfall stop in the location where the irrigation controller isinstalled.

According to some additional embodiments, a method for controllingirrigation based on rainfall comprises: providing an irrigationcontroller configured to execute one or more watering schedules;providing a server remote to a location where the irrigation controlleris installed, the server being in communication with the irrigationcontroller over a network; obtaining, via the irrigation controller,from the server and over the network, weather data associated with thelocation where the irrigation controller is installed; causing, via acontrol unit of the irrigation controller, an interruption of one ormore watering schedules executed by the irrigation controller inresponse to receipt, by the irrigation controller from the server, ofweather data indicative of active rainfall in the location where theirrigation controller is installed; and removing, via the control unitof the irrigation controller, the interruption after a completion of apredetermined interval of time in response to receipt, by the irrigationcontroller from server, of weather data indicative of a rainfall stop inthe location where the irrigation controller is installed.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features and advantages of severalembodiments of the present invention will be more apparent from thefollowing more particular description thereof, presented in conjunctionwith the following drawings.

FIG. 1 is a diagram of a rain sensor device for interrupting executionof one or more watering schedules of an irrigation controller accordingto several embodiments.

FIG. 2 is a variation of the rain sensor device of FIG. 1 according toseveral embodiments.

FIG. 3 is a functional diagram of the components of some embodiments ofa rain sensor unit of the rain sensor device of FIGS. 1 and/or 2.

FIG. 4 is a functional diagram of the components of some embodiments ofan interface unit of the rain sensor device of FIGS. 1 and/or 2.

FIG. 5 depicts a simplified flow diagram of a process for use inadjusting the mode of operation of the sensor unit of FIG. 3.

FIG. 6 depicts a simplified flow diagram of a process for use indetecting and inhibiting an irrigation cycle in accordance with oneembodiment.

FIG. 7A is one embodiment of the interface unit of the rain sensordevice of FIG. 4 illustrating user inputs and display outputs.

FIG. 7B is another embodiment of the interface unit of the rain sensordevice of FIG. 4 illustrating user inputs and display outputs.

FIG. 8 is another embodiment of the interface unit of the rain sensordevice of FIG. 4 illustrating user inputs and display outputs.

FIG. 9 depicts a simplified flow diagram of a process for use ininitializing the rain sensor device illustrated in FIGS. 1 and 2.

FIG. 10 illustrates a simplified flow diagram of a process for use inthe event that loss of communication occurs between the sensor unit andinterface unit of rain sensor device or system illustrated in FIGS. 1and 2.

FIGS. 11-19, 27A-B and 28 illustrate various embodiments of thecomponents of a rain sensor unit for use with a receiver unit forinterrupting execution of one or more watering schedules of anirrigation controller according to several embodiments.

FIGS. 20 and 21 graphically illustrate signal strength profiles used toapproximate the propagation environment over communication distancesless than the breakpoint distance at 915 MHz and 868 MHz, respectivelyaccording to one embodiment.

FIG. 22 illustrates an example implementation of a “TEST” operationalmode utilized during the installation of the sensor unit in accordancewith one embodiment.

FIG. 23 illustrates a simplified flow diagram of an exampleimplementation of a sleep or normal operational mode at the sensor unitof FIGS. 1 and 2, according to some embodiments.

FIG. 24 illustrates a simplified flow diagram of a process for use indetecting and inhibiting an irrigation cycle in accordance with oneembodiment.

FIG. 25 illustrates a simplified diagram of one implementation of thelow temperature operational mode according to some embodiments.

FIG. 26 illustrates one implementation of a “TEST” operational mode inaccordance with some embodiments.

FIG. 29A is another embodiment of the interface unit of the rain sensordevice of FIG. 4 illustrating user inputs and display outputs.

FIG. 29B is another embodiment of the interface unit of the rain sensordevice of FIG. 4 illustrating user inputs and display outputs.

FIG. 30 graphically illustrates example rain profiles and the points atwhich irrigation is interrupted or reactivated based on a rate of changeof a sensed amount of rain fall, according to some embodiments.

FIG. 31 illustrates a simplified flow diagram of one embodiment of theoverall operation of the rain sensor system 10.

FIG. 32 illustrates a simplified flow diagram of one embodiment of aprocess for installing and pairing the interface unit and the sensorunit of FIGS. 1 and 2 together.

FIG. 33 illustrates an exemplary embodiment of a modular irrigationcontroller having an interface unit module.

FIG. 34 illustrates a rain sensor system in which an interface unit ispaired and communicates with n sensor units 12 a-n according to someembodiments.

FIG. 35 illustrates a rain sensor system in which a sensor unit ispaired with and communicates with n interface units 14 a-n according tosome embodiments.

FIG. 36 is one embodiment of the interface unit of the rain sensordevice of FIG. 4 illustrating user inputs and display outputs.

FIG. 37 is functional diagram of the components of some embodiments ofan interface unit of the rain sensor device.

FIG. 38 is one embodiment of a user interface of the interface unit ofFIGS. 36 and 37 illustrating various user inputs and display outputs.

FIG. 39 illustrates one embodiment of the user inputs and displayoutputs of the user interface of FIG. 38 during initial power up.

FIG. 40 illustrates one embodiment of the user inputs and displayoutputs of the user interface of FIG. 38 when the system is pairing withthe rain sensor device.

FIG. 41 illustrates one embodiment a system communication and statusdisplay area of the user interface once the interface unit is pairedwith the rain sensor device.

FIG. 42 illustrates one embodiment of the system communication andstatus display area of the user interface during test mode between theinterface unit and the rain sensor device.

FIG. 43 is a chart illustrating signal strength and interaction with therain sensor device according to one embodiment.

FIG. 44 illustrates one embodiment of the user inputs and displayoutputs of the user interface of FIG. 38 once the interface unit hasbeen paired to the rain sensor device.

FIGS. 45a-d illustrate one embodiment of an irrigation mode display areaof the user interface of FIG. 38 depicting various irrigation modes.

FIGS. 46a-d illustrate one embodiment of a sensor data and thresholdsdisplay area of the user interface of FIG. 38 depicting various rain andtemperature indications.

FIGS. 47-49 illustrate one embodiment of the display outputs of the userinterface of FIG. 38 depicting the interaction between the irrigationmode display area and the sensor data and threshold display area.

FIGS. 50-53 illustrate one embodiment of the display outputs of the userinterface of FIG. 38 depicting the interaction between the irrigationmode display area and the sensor data and thresholds display area asvarious irrigation modes are implemented.

FIGS. 54-57 illustrate one embodiment of the display outputs of the userinterface of FIG. 38 during a light rain.

FIGS. 58-63 illustrate one embodiment of the display outputs of the userinterface of FIG. 38 during a heavy rain.

FIGS. 64-69 illustrate one embodiment of the display outputs of the userinterface of FIG. 38 during a low temperature condition.

FIG. 70 is an illustration of another embodiment of an interface unitfor use in the rain sensor system of at least FIGS. 1 and 2, which issimilar to the interface units of FIGS. 4 and 37.

FIG. 71A shown a graphical user interface displayed on the display ofthe interface unit of FIG. 70 displaying various pictorialrepresentations in accordance with some embodiments.

FIG. 71B shows a graphical user interface displayed on the display ofthe interface unit of FIG. 70 displaying various pictorialrepresentations in accordance with some embodiments.

FIG. 71C illustrates a graphical user interface displayed on the displayof the interface unit of FIG. 70 according to some embodiments.

FIG. 72 depicts an embodiment of the display of the interface unit ofFIG. 70 displaying an initial power up screen.

FIG. 73 illustrates an embodiment of the display of the user interfaceof FIG. 70 when the system is pairing with a rain sensor device toestablish a communication link.

FIG. 74 illustrates one embodiment of the display of the user interfaceof FIG. 70 once the interface unit has been paired to one or more rainsensor devices, and the system is in normal irrigation mode.

FIG. 75A illustrates an embodiment of the display of an interface unitwhen a sensed rainfall is above a rainfall threshold while a sensedtemperature is above a temperature threshold, where the combination ofrepresentations conveys to the user that the irrigation is interrupted.

FIG. 75B depicts the user interface displayed on the display of theinterface unit, in accordance with some embodiments.

FIG. 76 illustrates an embodiment of the display of an interface unitwhen a sensed temperature falls below the temperature threshold whilethe sensed rainfall is below the rainfall threshold and a rain event isnot identified, where the combination of representations convey to theuser that the irrigation is interrupted.

FIG. 77 illustrates an embodiment of the display of an interface unitwhen a sensed rainfall is above a rainfall threshold and a sensedtemperature falls below a temperature threshold, where the combinationof representations conveys to the user that the irrigation isinterrupted.

FIG. 78 illustrates an embodiment of the display of an interface unitwhere a combination of displayed representations informs a user that theinterface unit is in a bypass rain/freeze mode with the sensed rainfallbeing above the rainfall threshold and the sensed temperature beingbelow the temperature threshold.

FIG. 79 illustrates an embodiment of the display of an interface unitwith the combination of displayed representations conveying that theinterface unit is in an override halt irrigation mode.

FIG. 80A depicts a perspective view of an interface unit in accordancewith some embodiments.

FIG. 80B depicts another perspective view of the interface unit of FIG.80A.

FIG. 81 depicts a simplified representation of an insert, in accordancewith some embodiments, that can be cooperated with an interface unit,such as the interface unit of FIGS. 80A and 80B.

FIG. 82 depicts a simplified flow diagram of a process of controllingirrigation in accordance with some embodiments.

FIG. 83 depicts a simplified flow diagram of a process of settingparameters for use in controlling irrigation in accordance with someembodiments.

FIG. 84 depicts a simplified flow diagram of a process of controllingirrigation performed by an interface unit according to some embodiments.

FIG. 85 depicts a simplified flow diagram of a process of interfacingwith an irrigation controller based on rainfall via an interface unit,according to some embodiments.

FIG. 86 graphically illustrates an example rainfall accumulationprofile, a point at which irrigation is interrupted, and a point atwhich an interruption timer is started based on a sensed end ofrainfall, according to some embodiments.

FIG. 87 graphically illustrates an example rainfall accumulationprofile, a point at which irrigation is interrupted, a point at which anirrigation interruption timer is reset based on a sensed start ofrainfall, and two points at which an interruption timer is permitted tocontinue a countdown of the time remaining in the interruption ofirrigation based on a sensed end of rainfall, according to someembodiments.

FIG. 88 depicts a simplified flow diagram of a process of interfacingwith an irrigation controller based on rainfall via an interface unit,according to some embodiments.

FIG. 89 depicts a diagram of a system of controlling irrigation based onrainfall, according to some embodiments.

FIG. 90 is a simplified functional diagram of the components of someembodiments of a server.

FIG. 91 depicts a simplified flow diagram of a process of controllingirrigation based on rainfall, according to some embodiments.

FIG. 92 is a simplified functional diagram of the components of someembodiments of an irrigation controller.

FIG. 93 depicts a simplified flow diagram of a process of controllingirrigation based on rainfall, according to some embodiments.

FIG. 94 depicts a diagram of a system of controlling irrigation based onrainfall, according to some embodiments.

Corresponding reference characters indicate corresponding componentsthroughout the several views of the drawings. Skilled artisans willappreciate that elements in the figures are illustrated for simplicityand clarity and have not necessarily been drawn to scale. For example,the dimensions of some of the elements in the figures may be exaggeratedrelative to other elements to help to improve understanding of variousembodiments of the present invention. Also, common but well-understoodelements that are useful or necessary in a commercially feasibleembodiment are often not depicted in order to facilitate a lessobstructed view of these various embodiments of the present invention.

DETAILED DESCRIPTION

The following description is not to be taken in a limiting sense, but ismade merely for the purpose of describing the general principles ofexemplary embodiments. The scope of the invention should be determinedwith reference to the claims.

Referring first to FIG. 1, a diagram is shown of a rain sensor system 10for interrupting execution of one or more watering schedules of anirrigation controller 30 according to several embodiments. The rainsensor system 10 includes a sensor unit 12 having a first input/outputunit 16 and an interface unit or system 14 having a second input/outputunit 18. The first input/output unit 16 and the second input/output unit18 are coupled to each other by a communication link 15. The interfaceunit 14 is coupled to an irrigation controller 30 (either directly tothe controller via an interface 38, e.g., a rain sensor input, a commonline connection point or other such interface or input to the irrigationcontroller 30, or indirectly, e.g., coupled to the controller activationor output lines 32 or a common line 34, as illustrated in dashed lines).Alternatively, in some embodiments, the interface unit may beimplemented as a part of the irrigation controller. For example, in oneembodiment, the interface unit may be implemented as a module that maybe inserted into a modular irrigation controller. The irrigationcontroller 30 is programmed to execute one or more watering schedules.In one form, the irrigation controller 30 may output activation signals(e.g., 24 volt power signals) to respective ones of a plurality ofactivation lines 32, each coupled to a valve located in the region to beirrigated, an electrical switch to activate or deactivate lighting orother devices controlled by the controller 30. As is well known, one ormore sprinkler devices, drip lines and/or other irrigation devices maybe coupled to each valve.

The sensor unit 12 is typically located remotely from the interface unit14 in a position where it is exposed to rainfall. For example, thesensor unit 12 may be mounted to a rooftop, light pole, or telephonepole. In some embodiments the sensor unit 12 periodically obtainsmeasurements of parameters such as amount of rain fall, and/orprecipitation, temperature, and/or other parameters, and transmits theinformation to the interface unit 14. The interface unit 14 receives thedata from the sensor unit and processes it to determine whether toinhibit or interrupt irrigation. Additionally or alternatively, in someembodiments, the sensor unit may initiate transmission to the interfaceunit 14 once it detects a change in some atmospheric parameters, e.g.,amount of rain fall and/or temperature, and sends an update message tothe interface unit. In one embodiment, the message may include theamount of rain fall, temperature, battery strength, signal strengthand/or other data available at the sensor unit.

In some embodiments, once the interface unit 14 detects the beginning ofan irrigation cycle, it is instructed and/or is activated to communicatewith the sensor unit 12 to request information regarding measurementparameters, such as but not limited to precipitation data, temperatureand/or other such parameters. In one embodiment, the sensor unit 12receives the request, obtains the requested measurement data andtransmits the information to the interface unit 14. In someimplementations, the interface unit 14 receives instructions from theirrigation controller 30 requesting the interface unit 14 to transmit arequest to the sensor unit 12 requesting the measurement data.

In some embodiments, the interface unit 14 is located remotely from thesensor unit 12 and proximate to the irrigation controller 30 in alocation that is, in some implementations, accessible to the user. Theinterface unit is also coupled to the irrigation controller 30 (eitherdirectly or indirectly). In some embodiments the interface unit may beimplemented as a part of the irrigation controller and located on theirrigation controller. In one embodiment, for example, the interfaceunit may be implemented as a module that may be inserted into a modularirrigation controller.

In some embodiments, each interface unit 14 is specifically paired to asensor unit so that each rain sensor system 10 includes a paired sensorunit 12 and interface unit 14. Alternatively, in some embodiments eachinterface unit 14 is paired to more than one sensor unit 12. In theseembodiments, each sensor unit 12 is paired with the interface unitindependently. FIG. 34 illustrates a rain sensor system 10 in which theinterface unit 14 is capable of pairing and communicating with n sensorunits 12 a-n via communication links 15 a-15 n. Additionally, in one ormore embodiments, each sensor unit 12 is paired with more than oneinterface unit 14, wherein, the sensor unit is paired with each ofindividual interface unit 14 of the plurality of interface units. FIG.35 illustrates a system 10 in which the sensor unit 12 is capable ofpairing with and communicating with n interface units 14 a-n viacommunication links 15 a-15 n. The pairing may be implemented at thetime of purchase, at the time of installation, during batteryreplacement, one or more interface units can be paired with a singlesensor unit 12 after one or more other interface units are currentlyoperating and already paired with the sensor unit 12, or at other suchtimes. For example, a single sensor unit 12 within a community can beused by multiple different interface units each located at a differenthouse within the community. As such, a community developer can reducecosts by utilizing the single sensor unit 12 and pairing the multipleinterface units 14 a-n with the single sensor unit 12. As describedfurther below, the communication links 15 a-15 n can be wired orwireless, and are typically wireless.

The interface unit and sensor unit may be paired together using severaldifferent methods. For example, in one embodiment, the sensor unit 12and the interface unit 14 may be paired using a wired serial interface,e.g., the I2C (Inter Integrated Circuit bus) interface and protocol. Thepairing may be implemented using an additional 3 pin header connector(not shown) on both the sensor unit 12, and the interface unit 14, and ashort 3-wire cable (not shown) with matching receptacle connectors onboth ends, and a firmware procedure for executing the pairing uponconnecting both units together. This method of pairing the two unitsdiminishes problems created by side radio transmissions whenimplementing the pairing. Alternatively, the interface unit and thesensor unit may be paired by invoking a special mode of operation of theinterface unit 14, in which the ID information regarding the sensorunit's radio signal may be memorized and used for matching with the samesensor unit 12 in the future.

In another embodiment, pairing is implemented by temporarily positioningthe sensor unit 12 and the interface unit 14 close together and puttingthe sensor unit 12 in a high (preferably highest) power-transmissionmode with packets following each other without any gap between them andhaving a special pairing-mode identification bit, while the interfaceunit 14 is held in a low (preferably lowest) sensitivity mode. The closeproximity between the sensor unit 12 and the interface unit 14, combinedwith high-power transmissions from sensor unit and low-sensitivity ofthe interface unit help to eliminate any interfering emissions. Thechance of catching a side emission may be further diminished by using aspecific identifier for pairing mode, which helps eliminate any regulartransmission from other sensor units.

FIG. 32 illustrates one possible implementation of a process 3200 ofinstalling and pairing the interface unit 14 and the sensor unit 12together. At step 3210 the interface unit initiates a set up request andtransmits the request. The sensor unit 12 receives the request, in step3212, and continues to step 3214 where it determines whether or notcertain criteria are met. For example, the request message may compriseinformation about the interface unit 14. In one embodiment, the sensorunit 12 may use this information in step 3214 to determine whether it isable to pair up with the interface unit 14. For example, in someembodiments, the user may exert a manual force on a part of the sensorwherein the force fully depresses the plunger, the sensor unit willquery the rain sensor 318 and will use the measurement to determinewhether the plunger in the rain sensor 318 is fully depressed todetermine whether there is user authorization to pair up with aninterface unit.

Once the sensor unit determines that it is ready to pair up with theinterface unit, it will generate and send or transmit an acknowledgmentmessage to the interface unit in step 3216. The message may compriseidentification information about the sensor unit, and/or other datastored in memory of the sensor unit and/or available from the sensorsand or other devices coupled to the sensor unit 12. Additionally, instep 3216, the sensor unit may store information about the interfaceunit 14, for example, information received in the request message intoits memory. In step 3218, the interface unit then receives theacknowledge message, and pairs up with the sensor unit. For example, theinterface unit may store information about the sensor unit, received inthe acknowledge message and/or other available sources, into its memory.Additionally or alternatively, when performing step 3214, the sensorunit may also determine whether it is ready for set up by ensuring thata user input, e.g. authorization, has been entered.

Referring generally back to FIG. 1, the interface unit 14 receivesmeasurement data from the sensor unit 12 and processes this data todetermine if irrigation (such as programmed into an irrigationcontroller 30) should be permitted or interrupted. For example, in oneembodiment, the interface unit 14 determines whether a predeterminedrelationship exists between the received measurements detected and astored preset level or threshold and/or other criteria. For example, theinterface unit may determine if the signal indicative of an amount ofrain has exceeded a threshold level of rainfall, and/or whether arelationship exists between the signal and some criteria. For example,in one embodiment, the interface unit may use the informationtransmitted from the sensor unit 12 to determine a rate of change, forexample, for the rain fall accumulation, and determine whether the rateof change satisfies a predetermined relationship.

Additionally or alternatively, the interface unit may look at therelationship between the received measurements when processing the datato determine whether irrigation should be inhibited or interrupted. Forexample in one embodiment the interface unit receives the measurementsand analyzes the relationship between one or more of the amount ofrainfall, the rate of rain fall and the temperature. Alternatively insome instances, the information may be processed by the sensor unit 12,where the determination regarding the relationship may be made by thesensor unit, and the determination may then be transmitted to theinterface unit 14 by the sensor unit 12, e.g., in response to therequest from the interface unit 14. If the predetermined relationshipexists (e.g., the threshold level of rainfall has been exceeded by theamount of sensed or measured rain fall), the electronics of theinterface unit 14 and/or the controller 30 generate the appropriatesignaling to cause the interruption of the execution of wateringschedules by the irrigation controller 30.

This approach to overriding or interrupting watering based on measureddata, such as sensed rain fall amounts is fundamentally different thanthe approach of known rain sensor devices that interrupt controlleroperation when a threshold level of rain has been exceeded. That is,traditional rain sensors, such as described in U.S. Pat. No. 6,452,499to Runge et al., and U.S. Pat. No. 6,977,351 to Woytowitz (both of whichare incorporated herein by reference), employ a remote rain sensor thatsends a signal to its receiver to indicate that the rain threshold hasbeen exceeded, where the rain sensor initiates the communication andsends a signal to its receiver as soon as a rain threshold has beenexceeded. In contrast, according to several embodiments, the sensor unit12 sends measurement information to the interface unit 14, and theprocessing of the data and determination of whether or not to interruptand/or adjust irrigation occurs at the interface unit 14. Additionally,according to some embodiments, the interface unit 14 initiates thecommunication between the sensor unit 12 and the interface unit 14periodically or when it detects that an irrigation cycle is to beinitiated. The sensor unit 12 sends a signal to the interface unit 14after receiving a request or query from the interface unit 14.

It is also known that the threshold level of existing rain sensors maybe adjusted by making a mechanical adjustment to the sensor unit, suchas described in U.S. Pat. No. 6,570,109 to Klinefelter (which isincorporated herein by reference). However, since the sensor unit islocated on a roof top or other similar location such that it may beexposed to the environment and be relatively tamperproof, it is verydifficult to easily adjust the threshold level of rainfall that willtrigger the interruption of irrigation. Several present embodimentsaddress this concern by providing a manual adjustment of the thresholdlevel at the interface unit 14, since in some embodiments the interfaceunit 14 is the portion of the rain sensor system 10 that determines ifthe threshold has been exceeded. In other embodiments, the adjustmentmay be made at the interface unit 14 and/or controller 30 andtransmitted to the sensor unit 12. The interface unit 14 is typically ina location that is far more easily accessible to the user; thus, theuser may more easily adjust the rain threshold in use, e.g., to accountfor seasonal changes.

Additionally, known rain sensors only interrupt irrigation when the rainfall exceeds a fixed threshold. In contrast, according to severalpresent embodiments, the sensor unit 12 sends measurement data to theinterface unit 14 and the interface unit 14 analyzes the atmosphericmeasurement data to permit or interrupt irrigation based on one or moredifferent considerations such as the amount of rain fall, the current orsensed temperature, the rate of change in the rain fall amount ortemperature or the combination of several criteria.

With reference to FIGS. 1, 4, 36, and 37, in some embodiments, a system10 for interfacing with an irrigation controller 30 based at least onmeasurement data associated with rainfall includes an interface unit(e.g., interface unit 14 in FIG. 1 and interface unit 3700 in FIG. 37)including a housing (e.g., housing 3602 in FIG. 36) and a controller(e.g., controller 414 in FIG. 37), also referred to herein as a controlunit. In some embodiments, which will be described in more detail below,the interface unit 14 (using its the control unit 414) is configured tocause an interruption of one or more watering schedules executed by theirrigation controller (see, e.g., ref no. 30 in FIG. 37) separate fromthe interface unit 14. In one aspect, the interruption, by the controlunit 414, of the one or more watering schedules executed by theirrigation controller 30 is based on signaling received from a rainsensor (e.g., rain sensor 12 in FIG. 1 and rain sensor 3712 in FIG. 37),also referred to herein as a sensor unit, which is separate from theinterface unit 14.

In some embodiments, the rain sensor 12 includes a hygroscopic materialconfigured to expand in response to being contacted by rainfall and tocontract in response to a lack of rainfall and evaporation of absorbedmoisture. In other words, the hygroscopic material of the rain sensor 12is configured such that it expand in response to accumulating (e.g., byabsorption) moisture during active rainfall and contracts in response tolosing moisture (e.g., by drying out) when no rainfall is present. Inone aspect, the rain sensor 12 includes hygroscopic material in the formof a stack of one or more hygroscopic disks.

According to some embodiments, the control unit 414 of the interfaceunit 3702 is configured to cause an interruption of one or more wateringschedules executed by the irrigation controller 30 based on signalingreceived from a rain sensor 3712 when a sensed expansion of thehygroscopic material of the rain sensor 3712 is above a set rainfallaccumulation threshold parameter. The rainfall accumulation thresholdparameter, which will be discussed in more detail below, may be definedby being preprogrammed into the control unit 414 of the interface unit3702, or may be a user-defined adjustable parameter, e.g., selected froma plurality of user selectable accumulation threshold parameters.

In some embodiments, the control unit 414 of the interface unit 14/3702is configured to remove the interruption after a completion of apredetermined interval of time (e.g., 48 hours, 72 hours) after a sensedcontraction of the hygroscopic material of the rain sensor 12 that isindicative of a rainfall stop. Several embodiments of the function ofresuming interrupted irrigation a predetermined time duration followingdetected conditions evidencing the stop of rainfall are discussed inmore detail in the following paragraphs in connection with FIGS. 84-88.

FIG. 84 illustrates a flow chart of an exemplary process 8400 by whichthe control unit 414 of the interface unit 3702 operates wheninterfacing with an irrigation controller 30 to control irrigation, inaccordance to some embodiments. In particular, in step 8412 of theprocess 8400, the control unit 414 of the interface unit 3702 causes aninterruption of one or more watering schedules executed by theirrigation controller 30, based on signaling received from a hygroscopicmaterial-including rain sensor 3712, when a sensed expansion of thehygroscopic material of the rain sensor 3712 is above a set rainfallaccumulation threshold parameter. It is noted that in some embodiments,the decision to begin the interruption of irrigation may be accomplishedin accordance with any of the approaches described herein. It is alsonoted that in some embodiments, the beginning of interruption ofirrigation may be determined externally to the interface unit, e.g.,this determination and signaling of the beginning of an interruptioncould also be made at the sensor unit, such as may be done withtraditional rain sensor systems.

Next, in step 8414 of the method 8400 of FIG. 84, the control unit 414of the interface unit 3702 removes the interruption of one or morewatering schedules executed by the irrigation controller 30 after acompletion of a predetermined interval of time (e.g., 48 hours) after asensed contraction (e.g., a lack of expansion) of the hygroscopicmaterial indicative of a rainfall stop. As such, according to someembodiments described herein, the interface unit 3702 not onlyinterrupts irrigation after a certain preset threshold of rainaccumulation is met, but also maintains the interruption of theirrigation for a predetermined interval of time (e.g., 48 hours) after apoint in time when a stop of the rainfall is first detected. It is notedthat generally, the interface unit is configured to allow theinterruption for the predetermined interval of time following thedetection of the stop of rainfall, and that this detection may begenerally performed in a variety of ways, e.g., through the detection ofcontraction or lack of continued expansion of a hygroscopic material.

FIG. 85 depicts a simplified flow diagram of a process 8500 ofinterfacing with an irrigation controller 30 based on rainfall inaccordance with some embodiments. In step 8512, an interface unit 3702including a housing 3602 and a control unit 414 within the housing areprovided. Step 8514 of the process 8500 includes causing, via thecontrol unit 414, an interruption of one or more watering schedulesexecuted by the irrigation controller 30 that is separate from theinterface unit 3702. In step 8514 of the process 8500 illustrated inFIG. 85, the interruption of the one or more watering schedules executedby the irrigation controller 30 is based on signaling received from arain sensor 3712 separate from the interface unit 3702 and includinghygroscopic material, when a sensed expansion of the hygroscopicmaterial is above a set rainfall accumulation threshold parameter. Thehygroscopic material of the rain sensor 12 is configured to expand inresponse to being contacted by the rainfall and to contract in responseto an absence of the rainfall. Step 8516 of the process 8500 includesremoving, via the control unit 414, the interruption after a completionof a predetermined interval of time (e.g., 48 hours, etc.) after asensed contraction (e.g., a lack of expansion) of the hygroscopicmaterial indicative of a rainfall stop.

The interval of time for which the control unit 414 of the interfaceunit 3702 is configured to maintain an interruption of one or morewatering schedules executed by the irrigation controller 30 can be 24hours, 48 hours, 72 hours (or longer), and may be preprogrammed into thecontrol unit 414, or may be preset (and adjustable) by a user of theinterface unit 3702. It is understood that while example intervals oftime are provided, the interval of time may be any length of time thatis suitable to the needs of the overall watering system and balances theuse of water for irrigation and conserving water resources. That is, insome embodiments, the length of time should be long enough to ensurethat the benefit of natural watering to rainfall is provided withoutover or unnecessarily watering, and not be so long that the plant lifebeing watering is endangered due to lack of water. In somemunicipalities, laws or ordinances have been enacted to define thatirrigation be automatically interrupted during rainfall and for a periodof time. In one such example, in 2016, the state of Californiaintroduced a mandate against irrigating for 48 hours after a rainfall ofone-quarter inch or more. Accordingly, in some embodiments, the intervalof time is set to 48 hours or more.

In some aspects, the control unit 414 of the interface unit 3702 isconfigured such that, when the interface unit 3702 receives signalingfrom the rain sensor 3712 corresponding to a sensed contraction of thehygroscopic material of the rain sensor 12 indicative of a rainfallstop, the control unit 414 initiates a timer configured to count down aremainder of time left on the predetermined interval of time of theinterruption of the one or more watering schedules executed by theirrigation controller 30. For example, if the control unit 414 isconfigured such that the predetermined interval of time of theinterruption of irrigation after a sensed contraction of the hygroscopicmaterial indicative of a rainfall stop is 48 hours, after the interfaceunit 3702 receives signaling from the rain sensor 3712 corresponding toa sensed contraction or lack of expansion of the hygroscopic material ofthe rain sensor 12 indicative of a rainfall stop, the control unit 414initiates a timer configured to count down 48 hours from a point oftime. During active rainfall and during this 48 hour window followingthe stop of rainfall, one or more of the watering schedules executed bythe irrigation controller 30 will be interrupted by the interface unit3702. In some embodiments, while the timer activated by the control unit414 of the interface unit 3702 counts down the remainder of time left onthe predetermined interval of time of the interruption of irrigationafter a sensed stop of rainfall, the control unit 414 of the interfaceunit 3702 is configured to obtain an amount of expansion and contractionof the hygroscopic material of the rain sensor 12 in the signaling fromthe rain sensor 3712 at intermittent intervals. Such intermittentintervals can be pre-programmed into the control unit 414, or may be setand adjusted by the user of the interface unit 3702. Some examples ofthe intermittent intervals at which the control unit 414 of theinterface unit 3702 can obtain an amount of expansion and contraction ofthe hygroscopic material of the rain sensor 12 in the signaling from therain sensor 3712 include but are not limited to: 5 minutes, 10 minutes,15 minutes, 20 minutes, 25 minutes, 30 minutes, 35 minutes, 40 minutes,45 minutes, 50 minutes, 55 minutes, 60 minutes, 75 minutes, and 120minutes. The exact interval will likely be system dependent and afunction of the power usage and signaling protocol between the rainsensor and the interface unit.

In some embodiments, the control unit 414 of the interface unit 3702 isconfigured to determine that the signaling received from the rain sensor3712 at one of the aforementioned intermittent intervals during thetimer-based countdown indicates a contraction of the hygroscopicmaterial of the rain sensor 3712 relative to a measured amount ofexpansion and contraction of the hygroscopic material received from therain sensor 3712 at a preceding intermittent interval. In one aspect,based on such a determination, the control unit 414 permits the timer tocontinue the countdown of the remainder of time left on the interval oftime (e.g., 48 hours) of the interruption of irrigation. In other words,in some aspects, so long as the interface unit 3702 receives measurementdata from the rain sensor 3712 corresponding to a contraction (e.g., alack of expansion) of the hygroscopic material of the rain sensor 3712relative to a preceding received measurement, which is indicative of anabsence of rainfall and the drying out of the hygroscopic material ofthe rain sensor 3712, the control unit 414 of the interface unit 3702permits the timer to continuously count down to zero the remainder oftime left on the interval of time of the interruption of irrigation. Insome embodiments, after the timer counts down to zero the remainder oftime left on the interval of time of the interruption, the control unit414 removes the interruption of the one or more watering schedulesexecuted by the irrigation controller 30 (e.g., by activating a switch),thereby permitting the irrigation controller 30 to execute one or morewatering schedules in normal irrigation mode. In some embodiments, whendetermining if the received signaling indicates a contraction, more thanone measured amount from preceding intermittent intervals may be used.For example, the control unit may consider the current measurementrelative to the average of the three preceding measurements. In anotherexample, the control unit may consider the average of the three (orother number) current measurements relative to a prior measurement (oraverage of prior measurements).

In some embodiments, the control unit 414 of the interface unit 3702 isconfigured to determine that the signaling received from the rain sensor3712 at one of the aforementioned intermittent intervals indicates thatthe amount of expansion and contraction of the hygroscopic material ofthe rain sensor 3712 indicates an expansion of the hygroscopic materialrelative to an amount of expansion and contraction of the hygroscopicmaterial received from the rain sensor 3712 at a preceding intermittentinterval. In response to this determination, in some aspects, thecontrol unit 414 resets the aforementioned timer to restart thecountdown of the remainder of time left on the predetermined interval oftime of the interruption of irrigation. In other words, in some aspects,when, during a countdown of the predetermined interval of time of theinterruption of irrigation, the interface unit 3702 receives dataindicative of an expansion of the hygroscopic material of the rainsensor 3712, which is indicative of a renewed or continued rainfall andthe rewetting of the hygroscopic material of the rain sensor 3712, thecontrol unit 414 of the interface unit 3702 restarts the timer to thebeginning of the countdown. Then, if the timer counts down to zero theremainder of time left on the predetermined interval of time of theinterruption of irrigation with no intervening rainfall (which wouldagain reset the timer), the interruption of the one or more wateringschedules executed by the irrigation controller 30 is removed by thecontrol unit 414, and the irrigation controller 30 is permitted toexecute the one or more watering schedules in normal irrigation mode.

FIGS. 86 and 87 illustrate exemplary embodiments, where a decision tointerrupt one or more watering schedules irrigation executed by theirrigation controller 30 is based on signaling corresponding to anamount of expansion and contraction of a hygroscopic material of a rainsensor 12. FIG. 86 illustrates an exemplary graph of a measured rainfall accumulation amount in inches versus time in hours. In the exampleshown in FIG. 86, the interrupt (or rain fall cutoff) threshold 8602 isset at ½ inch, but it will be appreciated that the interrupt threshold8602 may be set at a different value (e.g., ½ inch, ¾ inch, 1 inch, 1½inch, 1½ inch, etc.) suitable for a location where the systems andmethods according to the embodiments described herein are implemented.In some aspects, the irrigation interrupt threshold 8602 is a user setor adjustable parameter, e.g., adjusted at the user interface unit. Inother aspects, the irrigation interrupt threshold 8602 is preprogrammedinto the control unit 414 of the user interface unit 14.

While referring to FIG. 86, concurrent reference is made to FIG. 88.FIG. 88 is a flow chart illustrating step-by-step logic of an exemplaryprocess 8800 performed by an interface unit 14 in interfacing with anirrigation controller 30 based on rainfall. In step 8812, the interfaceunit 14 receives, at periodic intervals (e.g., every 5 minutes, 15minutes, 30 minutes, 1 hour, etc.), signals including measurement datacorresponding to an amount of expansion and contraction of a hygroscopicmaterial (e.g., one or more hygroscopic disks) of the rain sensor 12,which indicates an amount of rainfall at or sensed by the rain sensor12. In the exemplary embodiment illustrated in FIG. 88, the measurementdata received from the rain sensor is represented by an amount ofmoisture at or sensed by the rain sensor 12, as indicated by line A inFIG. 86, which, as described above, represents a measured rain fallaccumulation amount in inches versus time in hours.

As described above, the signals transmitted by the rain sensor 12 to theinterface unit 14 may be transmitted via a wired or a wirelessconnection. Next, in step 8814 of the method 8800, the control unit 414of the interface unit 14 analyzes the measurement data received from therain sensor 12 and determines whether a certain relationship existsbetween the received measurement data and an interrupt (i.e., rainfallcutoff) threshold (e.g., ref no. 8602 in FIG. 86). In particular, in theembodiment shown in FIG. 88, if the control unit 414 of the interfaceunit 14 determines in step 8814 that the rainfall accumulation amount(as indicated by line A in FIG. 86 and corresponding to a level ofexpansion of one or more hygroscopic disks of the rain sensor 12) hasnot yet reached the interrupt threshold 8602, the interface unit 14 willnot cause an interruption of the watering schedules of the irrigationcontroller 30, but will permit the irrigation controller 30 to remain inoperational or normal mode, and will cycle back to step 8812 in order toobtain additional measurement data from the rain sensor 12 as describedabove.

If in step 8812, the interface unit 14 determines, based on signalingreceived from the hygroscopic material of the rain sensor 12, that therainfall accumulation amount (represented by line A in FIG. 86) hasreached the rainfall interrupt threshold (represented by line 8602corresponding to ½ inches of rain amount accumulation in FIG. 86), theprocess 8800 moves to step 8816, where the interface unit 14 causes aninterruption of one or more watering schedules executed by theirrigation controller 30. An exemplary point at which irrigation isinterrupted based on a measured level of rainfall accumulation is shownin FIG. 86 at 8604.

In some embodiments, in addition to causing an interruption of one ormore watering schedules executed by the irrigation controller 30, thecontrol unit 414 of the interface unit 14 is programmed to start atimer, which indicates and counts down a predetermined time intervalduring which the interruption of irrigation will be continuouslymaintained so long as the measurement data received from the rain sensor12 indicates a sensed contraction (e.g., a lack of expansion) of thehygroscopic material of the rain sensor 12 indicative of a rainfall stopand corresponding to a negative slope of line A in FIG. 86, and if nonew rainfall is sensed by the rain sensor 12 after the timer is started.In particular after the control unit 414 of the interface unit 14 causesan interruption of one or more watering schedules of the irrigationcontroller 30 in response to a sensed rain accumulation amount thatmeets the predetermined irrigation interruption threshold 8602 of FIG.86, the control unit 414 in step 8818 of FIG. 88 starts a timer to countdown a predetermined irrigation interruption interval (e.g., 48 hours)upon the expiration of which the control unit 414 removes theinterruption of irrigation and permits resumption of one or morewatering schedules of the irrigation controller 30. In other words, inthe embodiment shown in FIG. 86, the 48 hour countdown timer would beinitially started by the control unit 414 of the interface unit 14 atpoint 8604.

In FIG. 86, the predetermined time interval 8608 of the interruption ofirrigation is set for 48 hours by way of example only, and it will beappreciated that the predetermined time interval 8608 of theinterruption of the one or more watering schedules executed by theirrigation controller 30 after a detected rainfall stop (correspondingto a sensed contraction of the hygroscopic material of the rain sensor12 and a negative slope of line A) may be set for example, for 24 hours,72 hours, or for another time period suitable for a location where thesystem 10 is implemented.

With reference to FIG. 88, after the timer that counts down apredetermined irrigation interruption period after a detected rainfallstop is started in step 8818, in step 8820, the control unit 414 of theinterface unit 14 determines, at predetermined intermittent intervals(e.g., 1 minute, 5 minutes, 15 minutes, 30 minutes, etc.) whether therainfall accumulation measurement data received by the interface unit 14from the rain sensor 12 indicates an amount of a rainfallaccumulation-associated expansion of the hygroscopic material of therain sensor 12, or whether the rainfall accumulation measurement datareceived by the interface unit 14 from the rain sensor 12 indicates adryness-induced contraction of the hygroscopic material of the rainsensor 12 associated with a stop of the rainfall. In other words, atstep 8820, the control unit 414 of the interface unit 14 determineswhether the slope of line A in FIG. 86 is positive or negative.

If in step 8820 of FIG. 88 the control unit 414 of the interface unit 14determines that the measurement data received by the interface unit 14from the rain sensor 12 indicates a rainfall-induced expansion of thehygroscopic material of the rain sensor 12 (i.e., slope of line A ispositive), the control unit 414 resets the timer to restart thecountdown of the predetermined exemplary 48 hour time interval in step8822, and will cycle back from step 8822 to step 8812 in order to obtainadditional measurement data from the rain sensor 12 as described above.An exemplary point at which the timer would be reset by the control unit414 back to the beginning of the 48 hour irrigation interruptioncountdown based on a sensed expansion of the hygroscopic material of therain sensor 12 and the corresponding positive slope of line A is shownat 8610 in FIG. 86. Similarly, the control unit 414 would, at eachintermittent interval between the point 8610 and the peak of line A,reset the 48 hour timer based on a determination that the slope of lineA is positive relative to a preceding intermittent interval at whichmeasurement data was received, which is indicative of a continuedrainfall and a continued expansion of the hygroscopic material of therain sensor 12.

If in step 8820 of the method 8800 the control unit 414 of the interfaceunit 14 determines that the measurement data received at the newestintermittent interval by the interface unit 14 from the rain sensor 12indicates a dryness- (i.e., absence of rainfall, i.e., the slope is notpositive) induced contraction of the hygroscopic material of the rainsensor 12 (i.e., slope of line A is negative), the control unit 414permits the timer to continue the countdown of the exemplarypredetermined time interval (e.g., ref no. 8608 in FIG. 86) in step8824. In the example provided in FIG. 86, the initial point of anegatively sloped line A is 8606. At point 8606, the timer that countsdown the predetermined 48 hour countdown of the irrigation interruptionis not reset by the control unit 414, but is permitted by the controlunit 414 to continue the 48 hour countdown.

Similarly, the control unit 414 would, at each intermittent intervalbetween the point 8606 and the end of line A, permit the 48 hour timerto continue the countdown of the interruption of irrigation based on adetermination that the slope of line A is negative relative to apreceding intermittent interval at which measurement data was received,which is indicative of a continued absence of rainfall and a continuedcontraction of the hygroscopic material of the rain sensor 12. Anexemplary point at which the timer would be permitted to continue thecountdown of the 48 hour irrigation interruption interval 8608 based ona sensed contraction of the hygroscopic material of the rain sensor andthe corresponding negative slope of line A is shown at 8612 in FIG. 86.It is noted that in these embodiments, even when the sensed contractionof the hygroscopic material drops back below the original interruptthreshold 8602, e.g., at 8614, the slope will still be detected asnegative and irrigation will continue to be interrupted until expirationof the timer.

In an exemplary situation as depicted in FIG. 86, where the slope ofline A is continuously negative after the point 8606 when the slope ofline A initially turns negative, the timer that counts down the 48 hourinterruption interval 8608 of the one or more irrigation schedulesexecuted by the irrigation controller 30 will be permitted by thecontrol unit 414 of the interface unit 14 to continuously count down tozero (step 8824) until the predetermined exemplary 48 hour time interval8608 expires (step 8826). If, at step 8826, the control unit 414 of theinterface unit 14 determines that the 48 hour irrigation interruptioncountdown timer following a sensed stop of rainfall has not yet expired,the process 8800 then continues to obtain signals including dataindicating expansion or contraction from the rain sensor as in step8812, but shown in FIG. 88 as step 8827, the process continues back tostep 8820 to determine if the slope is positive or negative. In thisway, the timer will continue to countdown if the amount of expansion isbelow the original accumulation threshold (e.g., measurements are atpoint 8614 in FIG. 86. Conversely, if the control unit 414 of theinterface unit 14 determines at step 8826 that the timer counting downthe 48 hour irrigation interruption interval 8608 following the sensedstop of rainfall at point 8606 has expired, the control unit 414 removesthe interruption of one or more watering schedules of the irrigationcontroller 30 at step 8828, such that the irrigation controller canresume the one or more normal irrigation schedules, and the process 8800loops back to step 8812 as shown in FIG. 88.

FIG. 87 is generally similar to that shown in FIG. 86 and usescorresponding reference numerals to identify points that correspond tothe points depicted in FIG. 86, but additionally shows a situation,where the slope of line A, after being initially negative from the point8706, when the slope of line A initially turns negative, changes to apositive slope, for example, due to a restart of rainfall and theaccompanying measurement data indicating expansion of the hygroscopicmaterial of the rain sensor 12, which is sensed by the rain sensor 12and received by the control unit 414. In the exemplary situation shownin FIG. 87, this change from negative slope to positive slope of line Adue to a sensed rainfall accumulation corresponding to renewed rainfalloccurs above the irrigation cutoff threshold 8702 at a point 8714.

As described above, when in step 8820 of the method 8800 of FIG. 88 thecontrol unit 414 of the interface unit 14 determines that themeasurement data received by the interface unit 14 from the rain sensor12 indicates that the slope of line A has changed (i.e., at point 8714)from a negative slope (extending downward from point 8706) to a positiveslope (extending upward from point 8714) relative to the last set ofmeasurement data received from the rain sensor 12, the control unit 414resets the timer counting down the 48 hour irrigation interruptioninterval 8708 (as indicated by an X at the end of line 8708 in FIG. 88)and restarts the countdown of the exemplary 48 hour irrigationinterruption time interval at point 8714 of FIG. 87 in step 8822 of FIG.88. After this reset and restart of the 48 hour timer, the process 8800then cycles back to step 8812 in order to obtain additional measurementdata corresponding to an amount of expansion and contraction of thehygroscopic material of the rain sensor 12 as described above.

With reference to FIGS. 87 and 88, if in step 8820 at the nextintermittent interval when measurement data are received by the controlunit 414 from the rain sensor 12, the control unit 414 determines thatthe measurement data again indicates rainfall-induced expansion of thehygroscopic material of the rain sensor 12 (i.e., slope of line Acontinues to be positive as at point 8616 in FIG. 86), the control unit414 again resets the 48 hour irrigation interruption countdown timer andrestarts the countdown of the 48 hour predetermined irrigationinterruption time interval in step 8822 of FIG. 88, and will cycle backto step 8812 in order to obtain additional measurement datacorresponding to an amount of expansion and contraction of thehygroscopic material of the rain sensor 12 as described above.

If in step 8820 of the method 8800 the control unit 414 of the interfaceunit 14 determines that the measurement data received at the newestintermittent interval by the interface unit 14 from the rain sensor 12indicates a dryness (i.e., absence of rainfall) induced contraction ofthe hygroscopic material of the rain sensor 12 (i.e., slope of line Aturns negative), the control unit 414 permits the timer to continue thecountdown of the exemplary predetermined 48 hour time interval (e.g.,ref no. 8720 in FIG. 87) in step 8824. In the example provided in FIG.87, the initial point of a second negatively sloped segment of line A is8718. In the situation shown in FIG. 87, at point 8718, the countdowntimer of the predetermined 48 hour irrigation interruption interval 8720is not reset by the control unit 414, but is permitted by the controlunit 414 to continue the 48 hour countdown.

Similarly, the control unit 414 would, at each intermittent intervalbetween the point 8718 and the end of line A, permit the 48 hour timerto continue the countdown of the interruption of irrigation based on adetermination that the slope of line A is negative relative to apreceding intermittent interval at which measurement data was received,which is indicative of a continued absence of rainfall and a continuedcontraction of the hygroscopic material of the rain sensor 12. Anexemplary point at which the timer would be permitted to continue thecountdown of the 48 hour irrigation interruption interval 8720 based ona stop of rainfall and the subsequent sensed contraction of thehygroscopic material of the rain sensor 12 and the correspondingnegative slope of line A is shown at 8712 in FIG. 86.

In the exemplary situation depicted in FIG. 87, where the slope of lineA is continuously negative after the point 8718 when the slope of line Aagain turns negative, the timer that counts down the 48 hour irrigationinterruption interval 8720 of the one or more irrigation schedulesexecuted by the irrigation controller 30 will be permitted at step 8824by the control unit 414 to continuously count down to zero until thepredetermined 48 hour time interval 8720 of irrigation interruptionfollowing a sensed stop of rainfall expires. If, at step 8826 in FIG.88, the control unit 414 of the interface unit 14 determines that the 48hour irrigation interruption countdown timer following a sensed stop ofrainfall has not yet expired, the process 8800 then continues to obtainsignals including data indicating expansion or contraction from the rainsensor in step 8827, then continues back to step 8820 to determine ifthe slope is positive or negative as described above. Conversely, if thecontrol unit 414 of the interface unit 14 determines at step 8826 thatthe countdown timer of the 48 hour irrigation interruption interval 8720following the sensed second stop of rainfall (at point 8718 in FIG. 87)has expired, the control unit 414 removes the interruption of the one ormore watering schedules of the irrigation controller 30 at step 8828,such that the irrigation controller can resume the one or more normalirrigation schedules, and the process 8800 loops back to step 8812 asshown in FIG. 88.

It is noted that while some embodiments describe a rain delayinterruption timer initially starting when the interruption begins andis repetitively reset until the hygroscopic material begins to contract,in other embodiments, the timer is started on the first detection ofcontraction, and intermittently checked to determine if the contractionremains (as in FIG. 86) or does not persist (FIG. 87) in which case itwould be stopped, and then restarted again on the next detection ofcontraction. Referring now generally back to FIG. 2, other features aredescribed. In many embodiments, the sensor unit 12 sends data, andreceives requests or queries for sensed data from the interface unit 14through a communication link 15. The communication links 15 describedherein may be any wireline or wireless communication link. Generically,the interface unit 14 includes an input/output unit 18, which willcorrespond to the specific communication link 15. For example, in awireline communication link 15, the input/output unit 18 will be awireline signal transmitter, a wireline signal receiver and a wirelineconnector. However, in a two-way wireless communication link 40 (seeFIG. 2), the output takes the form of a wireless transceiver 44, such asa radio, optical, infrared, and/or ultrasonic transceiver. Furthermore,the input/output unit 16 of the sensor unit corresponds to thecommunication link 15. For example, in a wireline communication link 15,the input/output unit 16 will be a wireline signal transmitter, awireline signal receiver and a wireline connector. However, in awireless communication link 40 (see FIG. 2), the input/output unit 16takes the form of a wireless transceiver 42, such as a radio, optical,infrared, and/or ultrasonic transceiver. Advantageously, the wirelesscommunication link 40 of FIG. 2 allows for easier installation since awireline connection is not required between the sensor unit 12 and theinterface unit 14. It is understood that in some embodiments, both theinterface unit 14 and the sensor unit 12 each have a transmitter and aseparate receiver, instead of a transceiver, and in some instancesincludes input/output interfaces for both wired and wirelesscommunication.

The interface unit 14 may be coupled to the irrigation controller 30 indifferent ways depending on the controller 30 and user preference. Insome embodiments, the output lines 36 may be connected from aninput/output unit 20 of the interface unit 14 direct to an interface 38(e.g., a rain sensor input, a common line connection point or the like)of the controller 30. In the event the interface unit 14 determines orreceives an indication that a relationship exists between a threshold orother criteria and the measurement data and/or in the event that athreshold has been exceeded, a switch is closed within the output 20completing a circuit causing a current to flow through the output lines36 to the interface 38. The controller 30 is configured to sense thiscurrent, and in response, the controller 30 temporarily halts theexecution of one or more watering schedules and/or determines otherappropriate actions. The current flowing through the output lines 36 isswitched off after a period of time, in response to instructions orreset from the controller and/or in response to a data transmission, ora reply from the sensor unit 12 to a subsequent data request (e.g., whenthe precipitation data has returned to below the threshold level and/orthe relationship between the threshold level and other criteria and themeasured data no longer exists). In this case, the controller 30 sensesthe absence of the current at the interface 38 and resumes normalexecution of watering schedules. In another embodiment, the signal fromthe input/output 20 is a data signal that includes a message instructingthe controller 30 to temporarily halt execution of one or more wateringschedules until a subsequent resume data signal is sent.

In a further embodiment, rather than coupling to an interface 38 of thecontroller, the interface unit 14 couples in series with the common line34 of the activation lines 32. For example, the common line 34electrically passes through the output 20 (e.g., a switching device) ofthe interface unit 14. When the interface unit 14 determines or receivesan indication that a rain threshold has been exceeded and/or that othercriteria have been met, the interface unit opens the switching device,breaking the common line 34. This effectively disables all electricalsignals via the activation lines 32 to the valves, until the switch isclosed. In this way, the controller 30 is not aware that the wateringhas been interrupted or overridden. It is noted that in someembodiments, the interface unit 14 may be integrated into thefunctionality of the controller 30.

Alternatively, in some embodiments, the interface unit 14 may forwardthe measurement data or the determination that some criteria has beenmet, e.g., a threshold has been exceeded or other relationship existsbetween the measurement data and some criteria, to the irrigationcontroller 30, where the processor or the irrigation controller willinterrupt rain fall based on the received information.

In some embodiments the interface unit 14 may be implemented as a partof the irrigation controller 30 and/or located on or integral to theirrigation controller. In one embodiment, for example, the interfaceunit is implemented as a module that may be inserted into a modularirrigation controller. FIG. 33 illustrates an exemplary embodiment of amodular irrigation controller 3300 having an interface unit module 3312.The modular controller 3300 comprises a display 3302, a rotary dial3304, one or more user inputs 3306, a base module 3307, one or moreexpansion modules 3308, a sensor connection 3310, and an interface unitmodule 3312, all generally contained within a housing 3314. Generally,modular irrigation controllers are known in the art to be controllersthat accept expansion modules to provide additional station or zoneoutputs. Further details of various modular controllers are described inU.S. patent application Ser. No. 11/022,179 and published as U.S. PatentApplication Publication No. 2005/0273205, the entirety of which isincorporated herein by reference. In one embodiment, a base module 3307is provided that includes output connectors for the master valve (MV),common line (COM), and a number of station outputs (3 are illustrated inthe base module 3307). Each expansion module 3308 includes an additionalnumber of output connectors to allow connection of activation lines toactuate additional stations (in this case, three additional stationoutputs are provided with each module 3308).

In one embodiment, the interface unit module 3312 is coupled a modulemounting location instead of an expansion module. The interface unitmodule 3312 includes an antenna 3316 (one embodiment of an input/outputunit 18) to communicate with one or more sensor units 12. In oneembodiment, the interface unit module 3312 includes two connectors thatallow wires 3318 and 3320 to connect to the terminals or connections ofthe sensor connection 3310, where the sensor connection 3310 provides away to connect to the common line 34 without having to cut the commonline. It is noted that in this case, the wires 3318 and 3320 wouldreplace a wire connecting the two terminals of the sensor connection3310 together. In several embodiments, the interface unit module 3312 isnow coupled in series with the common line 34. When the interface unitmodule 3312 determines that irrigation should be interrupted or when itreceives an indication that a rain threshold has been exceeded and/orthat other criteria have been met, the interface unit module 3312 opensan internal the switch, breaking the common line 34. This effectivelydisables all electrical signals via the activation lines 32 to thevalves, until the switch is re-closed.

Alternatively, in another embodiment, the sensor connection 3310 isconfigured for connection to the controller of the modular controller3300. For example, when the interface unit module 3312 determines thatirrigation should be interrupted, the interface unit module 3312 causesa current to flow to the sensor connection. The controller detects thatpresence of current flow at the sensor connection, which indicates tothe controller that irrigation should be interrupted and the controllercauses the interruption. The controller of the modular controller 3300may be implemented through a single-processor or multiprocessor systems,microcontroller, minicomputers, microprocessor, processor, programmableelectronics and the like, and/or combinations thereof. In severalembodiments, the interface unit module 3312 gets operational power fromthe backplane connection of the module to the controller 3300. The aboveembodiments, allow the interface unit module 3312 to operate whenconnected to a module mounting location of the modular controller 3300without sending control signals directly from the module 3312 to thecontroller, since many modular controllers will not have sufficientprogramming to process such direct control signals. However, in otherembodiments, the interface unit module 3312 directly outputs irrigationinterrupt signals to the controller via the backplane connectionsbetween the module mounting location and the controller.

In one embodiment the interface unit module 3312 is inserted within themodular controller 3300, draws power therefrom and is coupled to aninterface unit 14 mounted externally. In this embodiment, according toone implementation, the interruption is controlled by the externalinterface unit 14. In one embodiment, the interface unit 14 sends thedetermination to interrupt irrigation to the interface unit module 3312and the interface unit module 3312 interrupts irrigation according toone or embodiments described above (e.g., breaks the common, or outputsa signal to the controller which interrupts irrigation). In anotherimplementation, the interface unit module 3312 includes a display andbuttons, etc., to create a user interface to allow a user to program theinterface unit module 3312 while it is inserted into the modularcontroller 3300. In another embodiment, the interface unit module 3312outputs signals to the controller of the modular controller 3300 anduses the user interface of the modular controller to allow the user toconfigure the interface unit module 3312.

Referring again back to FIGS. 1 and 2 and in a further embodiment, theinterface unit 14 will continue to indicate to the controller 30 that itshould remain off even after the precipitation data has returned belowthe threshold and/or other conditions no longer exist. For example, fora period of time after the precipitation data returns below thethreshold level, the interface unit 14 continues to allow current toflow to the interface 38, continues to send the appropriate controlmessage signaling to the interface 38, delays sending a control messageinstructing the controller to resume watering, or continues to break thecommon line 34. This delay in re-enabling the controller is settable bythe user on the interface unit 14 and allows the system to postponeirrigation for several days after a heavy rain has occurred. In otherembodiments, the delay can be automatically controlled, for example,using equations involving one or more of temperature, dry out rate, etc.This embodiment allows for increased water conservation.

In some embodiments, as illustrated in FIGS. 1 and 2, the interface unit14 and the sensor unit 12 are coupled via a two-way communication link15. The communication link 15 may be a wired communication, asillustrated in FIG. 1, or a wireless communication via communicationlink 40 as illustrated in FIG. 2. The two-way communication link 15enables the sensor unit 12 and the interface unit 14 to send and receivesignals, including one or more of data, status information and controlsignals to and from one another. For example, in one embodiment, theinterface unit 14 sends control signals to the sensor unit 12 and,depending on the control signal, the sensor unit 12 takes theappropriate action/s. For example, in one embodiment, the interface unit14 may send a request to the sensor unit 12 for data. The sensor unit 12may, in response to the request, generate the data and send it via thetwo-way communication link 15 to the interface unit 14. Further, in someembodiments, the interface unit sends control signals to the sensor unit12 over the two-way communication link 15, wherein the sensor unitreceives the signal and makes an adjustment or change based on thecontrol signal received. In one embodiment, the control signal from theinterface unit 14 causes the sensor unit 12 to change a mode ofoperation (e.g., such as entering a low power or hibernation mode).Additionally or alternatively, the sensor unit 12 sends signals, e.g.,including data, information and/or control signals, to the interfaceunit 14, and the interface unit is adapted to receive the informationand take actions and/or make determinations based on the information.For example, the sensor unit 12 may transmit information correspondingto an amount of rain and/or temperature sensed at the sensor unit 12.This information may be a measurement of rain fall or an indication thata threshold amount of received rain fall has been exceeded. In severalembodiments, the interface unit 14 receives a measurement of rain falland/or temperature and makes a determination of whether or not tointerrupt irrigation based at least in part on the receivedmeasurements. The interface unit 14 is adapted to cause an interruptionof irrigation if it is determined that irrigation should be interrupted.Further, the sensor unit 12 and interface unit 14 may both comprisetransceivers 16 and 18 (wired or wireless) wherein the transceivers arecapable of sending and receiving signals to one another over the two-waycommunication link 15. Alternatively, in one embodiment, the sensor unit12 and the interface unit 14 each have separate transmitter and aseparate receiver.

It is noted that in many embodiments, the interface unit 14 isconfigured to break the common line 34 of an irrigation controller. Inalternative embodiments, the interface unit 14 is coupled to and canbreak one or more individual activation lines 32. That is, the interfaceunit 14 may be coupled in series with one or more of the activationlines 32. When the interface unit 14 determines or receives anindication that a rain threshold has been exceeded and/or otherwisedetermines that irrigation should be interrupted, the interface unit 14opens the switching device, breaking one or more of the activationlines. In this embodiment, the interface unit 14 may be adapted tointerrupt irrigation for a specific set of activation lines whileallowing irrigation for valves coupled to other activation lines. Thebreaking of the one or more activation lines 32 disables the electricalsignals from those one or more activation lines 32 to the valves, untilthe switch is closed.

Referring next to FIG. 3, a diagram is shown of the functionalcomponents of some embodiments of a sensor unit 12 of the rain sensorsystem 10 of FIGS. 1 and 2. The sensor unit 12 includes a controller312, a memory 314, and a transceiver 316. The sensor unit furtherincludes and/or cooperates with a rain sensor 318. The controller 312may be implemented through a single-processor or multiprocessor systems,microcontroller, minicomputers, microprocessor, processor, programmableelectronics and the like, and/or combinations thereof.

The memory may be a separate memory unit within the sensor unit 12,external memory connected to the sensor unit via an interface (notshown), may be internal memory within the controller 312 as illustratedin FIG. 3, and/or other such configurations. In some instances, thecontroller 312 and the memory 314 together function as amicrocontroller. In some embodiments, memory 314 comprises one or moreof a random access memory (RAM), read only memory (ROM), Flash memory,an EEPROM memory, on-chip RAM, optical disk storage, and/or any othermedium which may be used to store the desired information and which maybe accessed by the controller. In some embodiments, the controlleremploys flash memory for storage of executable firmware, and is capableof being programmed “in-system”. This may be accomplished in someinstances by employing an in-system programming port in the sensor unit12 and/or on a printed circuit board, for example of the controller, foraccomplishing the programming process during a final assembly. In someembodiments, the controller further includes an EEPROM for non-volatilestorage of miscellaneous data to support at least some of thefunctionality of the controller. Additionally or alternatively, on-chipRAM may be present in sufficient quantity to provide functionalcapabilities in many embodiments.

The sensor unit 12, in some instances, further includes a power source324, such as a battery, solar cell, wind powered generated and/or othersuch power source, to power the components of the sensor unit 12. Forexample, the sensor unit 12 operates from a high capacity lithium-ionbattery. As illustrated in FIG. 3, in some embodiments, the controllerincludes an on-chip analog-to-digital converter (ADC) 326. The ADC may,for example, have an 8-bit resolution or greater, and contain four ormore input channels. In other embodiments, the ADC may be a separateunit within the sensor unit 12, or separate components within the sensorunit may comprise a separate ADC.

The transceiver 316 provides wired and/or wireless communication.Wireless radio frequency chips known in the art such as TexasInstruments CC1100, Melexis TH71211, Micrel MICRF112, or MICRF211,Semtech CE1201A, Atmel ATA5428, Analog Devices ADF7020 or ADF7021,and/or Maxim MAX7033 or MAX7044 may be used for the transceiver 316. Thewireless transceiver includes or couples to an antenna. In someimplementations, the transceiver comprises a single-chip transceiverthat provides an analog or digital Received Signal Strength Indicator(RSSI) output signal. If the RSSI output is an analog signal, it may besupplied initially to one channel of the ADC 326.

In some embodiments the sensor unit 12 may include and/or may couplewith several additional sensors, such as a temperature sensor 322, abattery voltage sensor 320 as shown in FIG. 3, and/or other suchsensors. The battery voltage sensor 320 is connected to the power source324. The temperature sensor 322 may be any temperature-sensitive devicesuch as a thermistor, temperature-dependent current device, and thelike. In some embodiments, the temperature sensor is capable ofdetecting an ambient temperature of between about, 150 to 0° F., forexample detecting an ambient temperature of about 35-39° F., e.g., 37°F., with a tolerance of ±5% or better.

The rain sensor 318 reacts to the presence of water and generally reactsproportionally to the amount of water (rain fall) received, for examplein one embodiment, the rain sensor generates an electrical signal thatis indicative of a level of precipitation or rain. This electricalsignal represents precipitation data. In some embodiments, the outputsignal is an output voltage signal of the rain sensor 318 that isprovided to one channel of the controller's ADC 326. In someembodiments, the level indicated by the electrical signal is transmittedto the interface unit 14 via transceiver 316 periodically and/or whenthe sensor unit determines that a change has occurred in the amount ofrain fall, and/or stored in memory for future access. For example, inthis or other embodiments, the level indicated by the electrical signalis stored in the memory 314 and upon receiving a request from theinterface unit 14 the controller 312 retrieves the data from the memory314 and forwards the data to the transceiver 316 to be transmitted tothe interface unit 14. Additionally or alternatively, the rain sensormay detect that a threshold level of rain or precipitation has beenreceived and in response generate a signal that indicates that thethreshold level of rain has been exceeded.

In other embodiments, the rain sensor may output signals from thetemperature sensor 322 and/or the battery voltage sensor 320 that may,for example, additionally or alternatively be provided to two otherchannels of the ADC 326, and the indicated levels stored in memory 314,to be supplied to the interface unit 14 periodically, upon detecting achange, and/or upon receiving a request from the interface unit. In someembodiments, the signal or measured levels may not be stored, andinstead the controller 312 may retrieve the information from one or moreof the sensors at the time of transmission and/or when a request isreceived from the interface unit 14. For example, in one embodiment thesensor unit 12 requests measurements from the sensors at fixedintervals, e.g., every 5 minutes, and may additionally process the datato determine whether a change has occurred since the last receivedmeasurement. The controller 312 may generate a data signal based on theelectrical signals received from the sensors, and may transmit the datasignal to the interface unit 14 via the communication link 15.

In some embodiments, the measured data transmitted to the interface unit14 is simply a measurement and does not include an indication that athreshold has been exceeded. Instead, the determination whetherirrigation should be permitted or interrupted (e.g., whether arelationship exists between certain criteria and the data, such as whena threshold has been exceeded) is made at the interface unit 14 and/orirrigation controller 30 based on the received measurements from thesensor unit 12. Alternatively, in other embodiments, the controller 312may be configured to determine if a predefined relationship existsbetween the measurement and a level or threshold, and transmit thatdetermination to the interface unit 14 upon receiving a request from theinterface unit 14. The sensor unit 12, in some implementations, does nottransmit measurement data regarding the information obtained through thesensors to the interface unit 14 unless and until it receives a requestfrom the interface unit 14 for such data. Alternatively, the sensor unit12 may transmit the measurement data to the interface unit 14 atintervals, e.g., 6 hour intervals, or when it determines a change in themeasurement data in addition to providing the data to the interface unit14 upon receiving a request for the data. Further, the information maysimply include an indication that a threshold has been exceeded. Inother implementations, the information provided may include a level ormeasure of rain.

In some embodiments, the rain sensor 318 comprises a sensor andcontroller circuitry where upon sensing a level of precipitation thesensor will cause an electrical voltage to be generated by the controlcircuitry. The sensor and circuitry may take different forms indifferent embodiments. By way of example, in some embodiments, the rainsensor 318 includes a moisture absorptive material that expands andcontracts based on the presence of and absence of rain fall, such as ahygroscopic material. The level or amount of expansion or contraction issensed or measured and provided as an electrical signal. The leveland/or measurement data is then transmitted by the transceiver 316 tothe interface unit 14, wherein in some implementations, the interfaceunit determines if a rain threshold has been exceeded and/or if otherrelationship exists between the measurement data and certain criteria.In some embodiments, the electrical signal corresponding to the level ofrain fall is converted to a measure of the amount of rainfall prior tobeing sent to the interface unit 14, and/or an indication of arelationship of the measurement relative to a threshold may be forwardedto the interface unit 14. Alternatively, the expansion of the absorptivematerial may cause activation of a switch when a preset level of rain isreached. Upon activation of the switch the control circuitry may send asignal to the controller and then store the indication in memory. Inthis embodiment, when a request from the interface unit is received forrain levels an indication that the preset level was reached istransmitted by the transceiver 316 to the interface unit 14. In someembodiments, the rain sensor will not generate any signals untilinformation is requested from the rain sensor, at which time the sensortransmits a signal indicating the measurement of rain fall or the signalindicating that the switch is activated. Alternatively, the sensor unit12 may initiate transmission to the interface unit 14 based on themeasurement data. For example, in one embodiment, the sensor unit 12will process the signal indicating the measurement of rain fall orsignal indicating that the switch has been activated to determine if achange in the atmospheric conditions has occurred. In this embodiment,if the sensor unit 12 determines that a change has occurred it willforward the signal to the interface unit 14. Additionally oralternatively, in one embodiment, the sensor unit will initiatetransmission to the interface unit 14 forwarding the signal at fixedintervals, e.g., every 6 hours. In some embodiments, the interface unit14 may send a request to the sensor unit 12 requesting that the sensorunit obtains current and/or updated data from the sensors prior to theinitiation of an irrigation cycle and/or at other times, for example,when the user requests the data through the user input, and or by othermeans. In some embodiments, for example, when the interface unitdetermines that an irrigation cycle is about to begin the interface unitmay send a message to the sensor unit 12 requesting current data todetermine whether to inhibit irrigation. In one exemplary embodiment,the interface unit may send a message to the sensor unit 12 requestingdata when the operator of the interface unit has requested the data. Forexample, in one exemplary embodiment, the operator may periodicallyrequest data, for example, through the user input 424 (see FIG. 4), toensure that the sensor unit 12 and the system 10 as a whole are workingproperly. The receipt of a signal from the sensor unit 12 with dataindicates that the sensor unit is properly working. Additionally, insome embodiments, the sensor unit 12 also sends its battery strength.This allows the operator send a test request message to the sensor unit12 to determine if it is working. Additionally, in some embodiments, thesensor unit 12 sends data indicating the battery strength or batterylife (and thus, approximately when the battery of the sensor unit willneed to be charged or replaced).

Alternatively, in embodiments where the sensor unit 12 initiatestransmission to the interface unit 14, the rain sensor may generate asignal comprising the measurements and/or other data and transmit thesignal to the interface unit 14 upon making some determination, e.g.,that a change in one or more parameters has occurred and/or othercriteria has been satisfied, and/or at fixed intervals.

The shape and configuration of the hygroscopic material may be varieddepending on the implementation. As described above, in someembodiments, the hygroscopic material is in the form of one or multipledisks. In other embodiments, the hygroscopic material is a granular andexpandable material within a flexible envelope or casing. For example,the granular material may include polyacrylamide or similar materials.

In several embodiments, the sensor unit 12 operates in one of severalmodes. The mode of operation may depend on one or more factors, such asbattery charge level or expected battery life, weather and/oratmospheric conditions, anticipated requests for data and/or other suchfactors. The modes may be adjusted internally by the controller 312and/or externally by the user via the user input 424 and/or by othermeans. In one implementation, the sensor unit 12 is in a sleep orquasi-powered down mode, which in some implementations, is a “normalmode”, which is in some embodiments the mode that the sensor unit 12 ismost often operating in. The sensor unit 12 reduces and/or attemptsminimize power consumption while in the sleep mode to better conservepower and/or maximize battery life. In some embodiments, while in thenormal or sleep mode the sensor unit 12 does not initiate a transmissionto the interface unit 14, and in some instance, will never initiate atransmission to the interface unit 14. In other embodiments, duringnormal or sleep mode the sensor unit will initiate transmissions to theinterface unit 14, for example at fixed intervals and/or when somecriteria are met, e.g., when there is a change in one of rain fall,temperature, and/or other parameters.

In some embodiments, while in the sleep mode, the transceiver 316 may besimilarly put into a sleep mode, where many of the components of thetransceiver are powered down, while the transceiver is still capable ofdetecting the presence of an incoming message without needing to applyfull power to all circuitry. In several implementations, during thesleep mode the sensor unit 12 is capable of receiving requests initiatedby the interface unit 14. The sensor unit may further receive requestsfor other information and/or operating parameters, such as requests forthe measurements received by the sensors employed with the sensor unit,the signal strength, the transmittal power, identification informationof the sensor unit, and/or a variety of other information. In oneembodiment, after receiving requests from the interface unit 14 and/orother devices, the controller 312 will determine what information isrequested, and will retrieve the information and/or initiate ameasurement of the requested information by the sensors. In someembodiments, the measurement(s) by sensors occurs periodically, and themeasurement data is forwarded to transceiver 316 and transmitted to theinterface unit via communication link 15. Alternatively, in someembodiments, the data obtained is stored onto the memory 314.

FIG. 23 illustrates an example implementation of a process 2300 ofoperating in sleep or normal mode at the sensor unit 12, according tosome embodiments. Normally, in the step 2302, the sensor unit is insleep mode. Accordingly, the sensor unit operates in a low battery usagestate with only minimal portions of the controller 414 running.Periodically, the sensor unit wakes up in step 2304. For example, thecontroller and other electronics of the sensor unit enter a normal powerusage mode. In step 2310, once awake, the sensor unit 12 queries thesensor/s and other devices and generates measurements. In someimplementations, these intervals are predefined. Alternatively, in otherembodiments, the sensor unit may adjust the rate at which it will wakeup and query the sensors based on the amount of rain fall, thetemperature, the rate of change of rain fall and/or temperature, and/orother such criteria. In some embodiments, the sensor unit 12 then storesthe measurements in the memory 314 for later processing. Alternatively,the sensor unit processes the data as soon as it is received from thesensors and other peripheral devices. Next, in step 2312, the sensorunit 12 processes the measurement data received from the sensors. Thesensor unit 12 may process the signals to generate measurements to besent to the interface units, and/or process the data to determinewhether the data satisfy certain relationships and/or criteria. Forexample, in one embodiment, the sensor unit 12 analyzes the datareceived from the rain sensor 318 and temperature sensor 322 todetermine a rate of rain fall, a rate of temperature and/or whetherthere is a change in the amount of rain fall and/or temperature.

In step 2314 the sensor unit 12 determines if a request for data hasbeen received from the interface unit 14. When the sensor unitdetermines that a request has been received, in some embodiments, theprocess continues to step 2320 where the sensor unit 12 transmits asignal to the interface unit. For example, the controller 312 of thesensor unit constructs a message comprising data such as the obtainedmeasurement data, e.g., rain fall and precipitation data, temperature,battery strength, signal strength of the received request, and/or otherdata into one or more data packets to be forwarded to the transceiver316 to be transmitted to the interface unit 14. The sensor unit thenreturns to the low power or sleep mode of step 2302.

Alternatively, if no request has been received from the interface unit14, the process moves to step 2316 where the sensor unit determines ifthere has been a change in the sensor data, for example, if there hasbeen a change in sensed atmospheric conditions and/or other criteriahave been met. For example, in one embodiment the sensor unit mayprocess the data to determine whether there is a change in the amount ofrain fall or temperature determined in step 2312. In one embodiment, thesensor unit may retrieve the results of the determination from thememory 314 to determine whether a change has occurred. Alternatively,the sensor unit may retrieve the data from the memory 314 for currentand previous data and/or query the sensors for the data before makingthe determination in step 2316. If the sensor unit 12 determines that achange has occurred in one or more of the sensor data, then the processwill continue to step 2320 where the sensor unit will send or transmit asignal to the interface unit comprising, for example, the measurementsretrieved from the sensors, signal strength, and/or other data availableat the sensor unit 12. The sensor unit then returns to the low power orsleep mode of step 2302. If, however, in step 2316 the sensor determinesthat no change has occurred in the atmospheric parameters, the processmoves to step 2318 where the sensor unit determines if it is time for aperiodic update to be sent to the interface unit. In one embodiment, thesensor unit 12 sends updates to the interface unit 14 at fixedintervals, e.g., every 6 hours. The updates may be sent to ensure theinterface unit that the sensor unit is working and that the connectionbetween the sensor unit and the interface unit 14 has not failed. If instep 2318 the sensor unit 12 determines that it is time for a periodicupdate, then it moves to step 2320 and sends a signal to the interfaceunit 14, and then returns to the sleep mode in step 2302. Alternatively,if it is not time for an update, then the sensor unit returns to step2302 when it enters sleep mode before then proceeding back to step 2304.

In some embodiments, the content of the message or packet may vary basedon different criteria or situation. For example, in one embodiment, thecontents of the packet may depend upon the type of request received fromthe interface unit. For example, a SENSOR_STATUS_REQUEST message may bereceived at the sensor unit from the interface unit 14. Upon receipt ofthis message, the sensor unit 12 initiates a measurement of theprecipitation level, ambient temperature, full-load battery voltageand/or other parameter depending on the received request according tosome embodiments. The sensor unit may query the sensors to obtain suchmeasurements, and/or retrieve the measurements from the memory 314.After these one or more measurements have been obtained, the sensor unit12 constructs a message packet containing the results of themeasurements along with the RSSI value that was observed during thereceipt of the message. The entire message packet is then transmitted tothe interface unit 14 in the form of a SENSOR_STATUS message. In someembodiments, in addition to information requests, while in the sleepmode, the sensor unit 12 may also receive “set” commands from theinterface unit 14. These commands provide a value for one or morevariables stored in memory within the sensor unit 12, such astransmittal power, threshold values, etc. Upon receiving such messages,the sensor unit 12 will store the value and transmit an acknowledgemessage to the interface unit 14.

In some embodiments, the sensor unit periodically monitors its storedpower level and/or battery life while in the sleep mode. A process 510by which the sensor unit monitors the battery life, according to someembodiments, is illustrated in FIG. 5. In step 512 the sensor unit 12transitions out of the sleep or low-power mode. In step 514 the sensorunit activates one or more sensors and/or other peripheral systems in orcooperated with the sensor unit 12. In some instances, the transmitterand/or transceiver is not powered up or only the transceiver or portionsof the transceiver are active.

The power or battery voltage level of the power source 324 is measuredin step 516. In step 518, it is determined whether to enter alow-battery mode. This determination may be made by comparing a measuredfull battery voltage level measured while the sensors and otherperipheral devices have been activated with a non-volatile constantvalue stored in memory 314 to determine if the power source 324 isnearing the end of its useful life or is below a threshold. In someembodiments, in order to accurately make this determination, thecontroller 312 may make a measurement of the ambient temperature, viathe temperature sensor, to calibrate the measured battery voltage. Ifthe battery is approaching the end of its life (e.g., the full-loadbattery voltage is below the minimum allowable voltage) the process 510continues to step 522 where the controller 312 switches the sensor unit12 into a low battery mode and attempts to reduce power consumption byeliminating or reducing the functions performed and/or the frequency ofperforming non-essential functions.

Once the sensor unit 12 enters a low battery mode, step 524 is enteredwhere the sensor notifies the interface unit 14 that it has detected alow battery condition. In some instances, the sensor unit 12 initiatesthe transmission of a warning message to the interface unit 14 at orbelow the transmission power last assigned by the interface. In step526, it is determined whether an acknowledgement has been received fromthe interface unit 14. If the acknowledgment is not received (typicallywithin a predefined period of time), the process continues to step 528where the transmission power is increased and the process returns tostep 524 to again transmit the warning message at the increased powerlevel. The power is increased with each subsequent attempt until anacknowledgment is received, a predefined number of attempts are madeand/or a predefined transmission power level is reached. In someembodiments, the loop through steps 524, 526 and 528 may be repeatedafter a period of time when an acknowledgement is not received.

In some embodiments when an acknowledgment is received from theinterface unit 14, the sensor unit 12 continues to step 530 where itadjusts the number of periodic updates it sends to the interface unit.For example, in one embodiment, where the sensor unit may send 4periodic updates each day to the interface unit during normal mode, onceit enters Low Battery mode the sensor unit may only send 1 periodicupdate per day to the interface unit. In some embodiments, the sensorunit 12 may also reduce the frequency at which it wakes up to query thesensors and/or other peripheral devices for information such as amountof rain, temperature, battery strength and/or other such data once itenters the Low Battery Mode of operation. Alternatively, in someembodiments, after receiving the acknowledge message, the sensor unit 12will not initiate further transmissions other than in response torequests received from the interface unit. The interface unit 14, uponreceiving the warning message, may notify a user, such as displaying amessage on a user display of the interface unit 14 alerting the user ofthe operational mode of the sensor unit 12. Returning to step 518, if itis determined that the end of battery life is not approaching the systemcontinues to step 520 where the sensor unit continues to operate and/orreturns to operating in normal or sleep mode.

In some embodiments, the sensor unit 12, will perform the batterymonitoring process 510 once per day to obtain a current battery voltagelevel and stores the measurement in memory 314, and/or forwards themeasurement to the interface unit 14. Alternatively, in someimplementations, it may not be necessary to perform battery monitoringprocess 510 often since the low battery usage of the sensor unit 12allows the battery or power source to function for long periods of time,and usage of power sources such as solar or wind power energy allowslonger battery life so that the monitoring of the battery life does nothave to be performed frequently.

Further, in some embodiments, the sensor unit may operate in a “LowTemperature” or “hibernate” mode. The sensor unit 12, according to somepossible implementations, may enter low temperature mode when itdetermines that the temperature is below a certain threshold. FIG. 25illustrates one possible implementation of the low temperatureoperational mode, according to several embodiments. In step 2510, whilein normal mode, the sensor unit will periodically, e.g. every 5 minutes,query the temperature and/or other sensors to determine the currenttemperature and other current values. Next, in step 2512 the sensor unit12 will process the measurements and uses the measurement to determineif a certain relationship exists between the measurements, e.g.,temperature, and a freeze threshold level in step 2514. For example, afreeze threshold level may be set at 36 degrees Fahrenheit. If in step2514, the relationship does not exist, the sensor unit will remain innormal mode (step 2516) and cycle back to step 2510. If in step 2514,the sensor unit determines that the relationship exists, the processwill move to step 2518 where it will generate and send a low temperaturemessage or warning to the interface unit 14. Next, in step 2520 thesensor unit receives an acknowledgment message from the interface unit.In one embodiment, when the sensor unit 12 sends the low temperaturemessage or warning and does not receive an acknowledgment it mayretransmit the message for a certain period of time, e.g., five minutes,and or a certain number or retransmissions until acknowledgment isreceived. In some embodiments, the sensor unit 12 will increase itstransmit power with each retransmission up to its maximum allowedtransmit power. In one embodiment, if the acknowledgment is not receivedafter the certain period of time and/or the certain number ofretransmissions the sensor will monitor the ambient radio noise todetermine if a certain level of noise exists. If the sensor unit 12determines that noise exists, the sensor unit will wait a certain amountof time and check back to see if the noise goes away. When the sensorsees an opportunity to send in a noise free time period, it willretransmit the temperature message. In one embodiment, when the sensorunit determines that a noise free time does not exist, and or is notcapable of retransmitting after a certain period of time, the sensorunit 12 will assume that the interface unit 14 is broken, has lost poweror is powered down. Accordingly, the sensor unit 12 will stop trying tocommunicate and listens periodically to see when the interface unit isready for communications and can receive transmissions. In someembodiments, when the interface unit does not hear a response from thesensor unit, the interface unit will cease transmissions so as not toclutter the air waves and listens constantly for communications from thesensor unit 12.

After the sensor unit 12 receives the acknowledgement message, it entersthe low temperature mode in step 2522. In one embodiment, the sensor maydecrease the rate at which it sends updates to the interface unit 14.Additionally or alternatively, the sensor unit may also decrease thefrequency at which it wakes up to query the sensors and/or other localor peripheral devices for data. While in the low temperature mode, instep 2524 the sensor unit will query the temperature and/or other data.Next, in step 2524 the sensor unit uses the sensed temperature data todetermine if the condition still exists at fixed intervals, e.g. onceper day. For example, the sensor unit 12 may measure the temperature anddetermine whether the temperature exceeds a certain threshold. When, instep 2526 the sensor unit determines that condition still exists, e.g.,that the temperature is still below a certain threshold level, in step2528 the sensor unit generates an update message comprising themeasurement of temperature and possibly other data and transmits themessage to the interface unit 14. Further, in step 2528 the sensor unitmay make certain determinations to adjust its mode of operation, whileremaining in low temperature mode. For example, in several embodiments,the sensor unit will measure the battery strength to determine if itneeds to enter into the low battery mode. Next, the sensor unit returnsto step 2524 where it will periodically, e.g. once per day, andprocesses the measurements, in step 2526 to determine if the atmosphericconditions have returned to a normal condition, e.g. temperature isabove the threshold. When in step 2526 the sensor unit determines thatthe conditions have returned to normal, e.g. the relationship betweenthe temperature and/or other data and the threshold no longer exists, instep 2530 the sensor unit will query sensor and other local sensor anddevices for data such as rain amount, temperature, battery strength,signal strength and/or other data and transmits an update message to theinterface unit 14 in step 2532 comprising some or all of the data. Next,in step 2534 the sensor unit enters Normal mode and the process willbegin again at step 2510.

The sensor unit 12 may also operate in a “test mode” in someembodiments. In many embodiments the test mode is utilized, in part,during the installation of the sensor unit 12 to provide the installerwith a relatively quick and simple-to-understand process for testingthat the sensor unit 12 is installed at a location with, for example,adequate radio reception from the interface unit 14. The installationprocess is described in further detail below.

Referring next to FIG. 4, a diagram is shown of the functionalcomponents of some embodiments of the interface unit 14 of the rainsensor device of FIGS. 1 and 2. The interface unit 14 comprises atransceiver 412, a controller 414, a relay device 416, a memory 418, auser display 426, and a user input 424. In some embodiments, theinterface unit 14 may also include a current sensor 420, and a voltagesensor 422. The components of the interface unit 14 are coupled to oneanother by a bus or other means. The transceiver 412 may be any hardwire, wireless, optical and/or other device capable of transmitting andreceiving signals to and from the interface unit 14 via thecommunication link 15 or 40. Examples of wireless radio frequency chipsknown in the art include Texas Instruments CC1100, Melexis TH71211,Micrel MICRF112, or MICRF211, Semtech CE1201A, Atmel ATA5428, AnalogDevices ADF7020 or ADF7021, and/or Maxim MAX7033 or MAX7044 may be usedfor the transceiver 316. The wireless transceiver includes or couples toan antenna. The controller 414 may be implemented through asingle-processor or multiprocessor systems, microcontroller,minicomputers, microprocessor, processor, programmable electronics andthe like, and/or combinations thereof. The controller 414 and the memory418, in some implementations, together function as a microcontroller.The memory 418 may be a separate memory unit within the interface unit14, external memory connected to the interface unit via an interface(not shown), may be internal memory within the controller 414, and/orother such configurations. Further, the memory may comprise one or moreof flash memory, EEPROM memory, RAM, ROM, on-chip RAM, and/or other suchmemory or combinations of memory.

In some embodiments, the controller 414 employs flash memory for storageof executable firmware, and is capable of being programmed “in-system”.This may be accomplished in some instances by employing an in-systemprogramming port in the interface unit 14, on a printed circuit board ofthe controller 414 and/or other configurations to accomplish theprogramming process during, for example, a final assembly. In someembodiments, the controller 414 further includes an EEPROM or othernon-volatile memory for storage of data, executables and/or othersoftware to support of the functional capabilities of the controller414. Additionally or alternatively, on-chip RAM may be included on thecontroller 414 in sufficient quantity for functional capabilities inmany embodiments. Generally, the controller 414 executes instructions,which in some instances are defined by processor and/or computerexecutable program codes or the like, stored in the memory 418 toimplement the functionality of the interface unit 14.

FIG. 24 illustrates a process 2400, according to some embodiments, bywhich, at least in some part, the interface unit 14 provides somecontrol over irrigation. When the sensor unit 12 transmits a signal tothe interface unit 14, the signal is received at the interface unit instep 2412. In some embodiments, the sensor unit 12 will transmit thesignal at fixed intervals, e.g., every 6 hours, and/or when it senses achange, for example, a change in the amount of rain fall or temperature.Additionally, the sensor unit 12 will send signals to the interface unit14 when the interface unit sends a request to the sensor unit requestinginformation as shown in optional step 2410. Alternatively, the signalmay be received in response to a request for data sent from theinterface unit in step 2410.

After receiving the signal, in step 2416, the interface unit processesthe signal to retrieve data such as temperature, amount of rain fall,and/or other data, such as battery strength. After processing the data,step 2422 is entered where the interface unit determines if irrigationis currently interrupted, e.g., if a relay or switch is currently open.When irrigation is not interrupted, in step 2418, the controller of theinterface unit 14 will determine whether to interrupt irrigation. Forexample, in one embodiment, in step 2418, the interface unit comparesthe measurements received from the sensor unit to certain thresholdlevels and/or other criteria to determine whether a relationship existsbetween the measurements, e.g., amount of rain fall and/or temperature,rate of change thereof and the thresholds. Further, in one or moreembodiments, the interface unit 14 may use the data to determine arelationship between current data and previous data received from thesensor unit. For example, in one embodiment the interface unit maydetermine a rate of change in the atmospheric data, e.g., rainfall,temperature, and/or other data. In some embodiments the decision tointerrupt the irrigation is based on whether the measurement dataexceeds certain preset thresholds. Additionally and/or alternatively thedetermination may be based on other criteria. For example, in oneembodiment the sensor unit uses the data to determine a rate of change,and bases the determination at least in part on the calculated rate ofchange.

FIG. 30 illustrates one example of how the decision to interruptirrigation may be based at least in part on the rate of change in theamount of rain fall. An example graph of rain fall amount in inchesversus time in hours is illustrated with two different rain fallprofiles A and B. In profiles, the rain fall cutoff (or interrupt)threshold 3002 is set at ½ inch. In profile A, the rate of increase ofrainfall is high (indicated by a steep slope on the increasing side ofprofile), and therefore, in some embodiments, the interface unit 14 willinterrupt irrigation before the threshold level is reached, for exampleat point 3004. Alternatively, in profile B, rate of increase of rainfall is less (indicated by the gradual slope of the increasing side ofthe profile), and in that situation, the interface unit 14 may inhibitirrigation after the rain fall amount reaches and/or exceeds thethreshold 3002, for example at point 3006. Thus, when determiningwhether to interrupt irrigation, several embodiments, use at least therain fall measurement and a rate of rain fall.

Referring back to FIG. 24, when in step 2418 the interface unitdetermines that irrigation should be interrupted it will generate aninterrupt signal in step 2420. For example, in one embodiment, theinterrupt signal is a signal to open a relay or switch to break thecommon line of the irrigation controller. Alternatively, if in step 2418the interface unit determines that irrigation should not be interrupted(irrigation should be permitted) it may continue to step 2430 where itmay determine whether irrigation should be adjusted. Criteria similar tothe determination of whether irrigation should be interrupted may beused to make the determination in step 2430. If the interface unitdetermines that irrigation should be adjusted, it may generate a signal,in step 2432, that cause an adjustment to the irrigation schedule oramount of irrigation. Alternatively, if the interface unit determinesthat an adjustment is not necessary it returns to step 2412 or optionalstep 2410 and repeats the process once a request is initiated and/or atransmission from the sensor unit is received. Alternatively, in someembodiments, once in step 2418 the interface unit determines thatirrigation should not be inhibited it returns to step 2412 or optionalstep 2410 and repeats the process once a request is initiated and/or atransmission from the sensor unit is received.

Returning to step 2422, when the interface unit determines thatirrigation is currently interrupted, in step 2424 the interface unit 14determines whether irrigation should be reactivated. For example, theinterface unit uses the data from step 2416 and determines whethercertain relationship exists between the data and certain levels and orthresholds. For example, the interface unit determines whether arelationship exists between a rain fall threshold and the amount of rainfall indicated by the data received from the sensor unit 12.

Additionally or alternatively, the interface unit may look at the rateof change in one or more atmospheric parameters to determine whether toreactivate irrigation. For example, in FIG. 30 the rate of rain fall inprofile A indicates a gradual decrease in the amount of rain fall at thesensor unit 12 (i.e., it represents a gradual decrease or drying out ofthe sensor material, possibly indicating further rain or slowing rain).As such, the interface unit may reactivate or permit irrigation afterthe amount of rain fall is below the threshold level, for example, atpoint 3008. Alternatively, in profile B the rate of rain fall decreaseis greater (as indicated by the decreasing slope of profile B).Therefore, the interface unit may reactivate or permit irrigation beforethe rain fall amount has fallen below the threshold 3002, for example atpoint 3010. A rapidly decreasing slope could indicate that the rain fallquickly stopped and perhaps that the air is dry such that irrigationshould be permitted sooner.

Returning to FIG. 24, if in step 2424 the interface unit determines thatirrigation should be reactivated or permitted it may generate a signalto reactivate irrigation in step 2426. For example, in one embodiment,the signal may cause a relay or switch breaking the common line of acontroller to close. This would allow irrigation activation lines of thecontroller to function. Alternatively, if in step 2424 the interfaceunit 14 determines that irrigation should remain interrupted, it willreturn to step 2412 or optional step 2410 and repeats the process once arequest is initiated and/or a transmission from the sensor unit isreceived.

FIG. 6 illustrates an alternative process 610 to, at least in part, toprovide some control over irrigation as implemented through theinterface unit 14, according to some embodiments. When an irrigationcycle is initiated or commanded by the irrigation controller 30, theinterface unit 14 is notified (e.g., a current flows in the common line34 that is detected by the interface unit). In step 612, the interfaceunit detects the initiation of an irrigation and/or the notificationthat an irrigation is about to be initiated, for example, the currentsensor 420 detects the current flow through the common line. Followingdetection of the signal, in step 614 the current sensor 420 notifies thecontroller 414 and the controller initiates a transmission of a requestto the sensor unit 12 by the transceiver 412. Alternatively, in someembodiments the current sensor sends a signal to the controller 414indicating the measurement of current flow and the controller determineswhether an irrigation is about to be initiated. Following the detectionof initiation of an irrigation cycle step 614 is entered where thecontroller 414 initiates a transmission of a request to the sensor unit12 by the transceiver 412. In step 616, the transceiver 412 receives asignal carrying data transmitted by the sensor unit 12 in response tothe request, and supplies the data to the controller 414. In someinstances, the signal provides measurement data taken by the sensor unit12 and/or an indication that a threshold has been reached, and themeasurement data or indication is stored or cached in the memory 418. Insome embodiments, the interface unit 14 may send a request to the sensorunit 12 requesting that the sensor unit obtains current and/or updateddata from the sensors prior to the initiation of an irrigation cycle. Insome embodiments, for example, when the interface unit determines thatan irrigation cycle is about to begin the interface unit may send amessage to the sensor unit 12 requesting current data to determinewhether to inhibit irrigation.

In step 618, the interface unit 14 determines whether the irrigationcycle should be inhibited. Alternatively, the measurement data isforwarded to the irrigation controller 30 to evaluate and determinewhether irrigation is to be interrupted. The signals received at theinterface unit 14 from the sensor unit 12 may comprise an indicating athreshold level has been exceeded, data corresponding to a level ofprecipitation and/or rain fall, and in some instances may furtherinclude other measurement data, such as temperature data sensed by thesensor unit 12. In one embodiment of determining in step 618 of whetherto inhibit irrigation, the controller 414 compares the measurement ofprecipitation and/or rainfall to some criteria, e.g., a stored thresholdlevel, to determine whether a predetermined relationship exits betweenthese variables (e.g., if the amount of measured rain fall exceeds athreshold level of rain). In some embodiments, the determination ofwhether the irrigation cycle should be inhibited comprises one or morecriteria, wherein the interface unit 14 and controller 414 processes thedata received from the interface unit to determine whether certaincriteria is met and based on this determination the interface unit maygenerate an interrupt message inhibit irrigation. In one embodiment, forexample, the interface unit 14 uses the information received from thesensor unit to determine a rate of change of the received atmosphericmeasurements, the interface unit may then generate an interrupt messageto inhibit irrigation when it senses a certain level of change in thereceived measurements, e.g., a positive rate of change in amount ofprecipitation or the rate of change of temperature, and/or other suchdata. In some embodiments, the instruction set operating in theinterface unit 14 is calibrated to correlate the information receivedfrom the sensor unit 12 to a level of rainfall that may be related tothe threshold level or other criteria. For example, in embodiments wherethe signal received at the interface unit 14 represents a raw electricalsignal output from the sensor unit 12, the transceiver 412, thecontroller 414 and/or other intermediate device processes this signal tocorrelate this signal to a corresponding level of rain fall.Alternatively, this correlation may be performed by the sensor unit 12,and the resulting correlation is forwarded to the interface unit 14. Insome embodiments, when the rain fall relationship does not exist thecontroller 414 may further compare other parameters, such as thereceived measurement of temperature to a stored temperature thresholdlevel to determine whether a predetermined relationship between thesevariables exists (e.g., if the measured temperature is below a thresholdtemperature). In other embodiments, the determination of whether arelationship exists between the measured rain level and a presetthreshold, or whether other variables such as temperature exceed apreset threshold, is made at the sensor unit 12 and the signal receivedby the interface unit 14 from the sensor unit 12 provides thesedeterminations from which the controller 414 determines whether toinhibit irrigation.

Once the controller 414 determines that irrigation should be inhibitedin step 618 (e.g., the threshold level of rainfall has been exceeded bythe amount of sensed or measured rain fall or the threshold level oftemperature is above the measured ambient temperature), the process 610continues to step 620 where the controller 414 generates an interruptsignal. In some forms, a relay device which is normally closed isopened, interrupting irrigation. In some embodiments, the relay deviceis implemented as a switching device which is opened to inhibit theirrigation. In step 622 when irrigation is being commanded by theirrigation controller 30 while the interface unit 14 is commanding thatirrigation be inhibited, a voltage sensor 422 monitors the voltageacross the relay contacts. In step 624, it is determined whether theirrigation cycle has terminated. When the irrigation cycle has notterminated, the process 610 returns to step 622 to monitor theirrigation cycle. When the irrigation cycle has terminated, the processmoves to step 626 where the interface unit 14 closes the relay device.Following step 626 the process returns to step 612 where the interfaceunit determines whether an irrigation cycle is initiated (e.g., thecurrent sensor device 420 monitors the current flow to determine if anirrigation cycle is detected).

Returning to step 618, when it is determined that irrigation should notbe inhibited, the system returns to step 612 to determine whether anirrigation cycle is detected. In some embodiments, the determinationthat irrigation should be inhibited (e.g., that a relationship existsbetween the measured variables and the thresholds) is made at the sensorunit 12, and upon transmitting a request to the sensor unit, theinterface unit 14 will receive an “irrigate” or “inhibit” command.

In some embodiments, when it is determined in step 618 that theirrigation is not to be interrupted (e.g., the level of rain fall orambient temperature do not meet the predetermined relationship),optional step 630 is entered where the interface unit determines whetherthe level(s) of the measurement data (e.g., rain fall, temperatureand/or other data) are such that the irrigation should be adjusted. Thismay be done by comparing the precipitation data and/or the temperatureto a second set of thresholds. Additionally or alternatively, theinterface unit 14 may forward one or more of the measurement data to theirrigation controller 30 allowing the irrigation controller to determinewhether irrigation is to be adjusted.

When it is determined in step 630 that the irrigation is to be adjusted,step 632 is entered and the interface unit 14 adjusts the run time ofthe irrigation cycle and/or notifies the irrigation controller 30 thatthe runtime should be adjusted (e.g., by forwarding measurement levelsand/or adjustments to be implemented). When it is determined in step 630that adjustments are not to be made or following step 632 the process610 returns to step 612 to detect the start of an irrigation cycle.

Referring back to FIG. 4, the user input 424 allows a user to input andadjust the stored threshold level(s), enable or disable the sensor(s),and/or adjust other settings. Generically, in one embodiment, the userinput 424 comprises at least one selectable user input that allows theuser to make adjustments and/or selections. The user input 424 maycomprise one or more of buttons, switches, levers, rotating dials, etc.The user display 426 may indicate the operational status of theinterface unit 14, e.g., the display may indicate that the receiver unitis powered on, what threshold level is selected, if the receiver unit isin an irrigation interrupt state, etc., and/or the operational status ofsensor unit 12 such as the operational mode of the sensor unit. The userdisplay 426 may be one or more of a display screen, liquid crystaldisplay (LCD), touch screen display, lights, LEDs, and/or other relevantdisplays. In some, embodiments for example, the display comprises abacklit LCD, for example, which is capable of displaying alphanumericcharacters with 11-segment LCD digits. It is noted that although theinput/output unit 18 (whether wired or wireless) is illustrated as atransceiver (wired or wireless), in some embodiments the input/output 18may comprise a separate transmitter and receiver.

FIG. 7A is an illustration of some embodiments of the interface unit 14for use in the rain sensor system 10 of FIGS. 1 and 2. In thisembodiment, the user input 424 is embodied as including an ON/OFF switch712, an up button 714 and a down button 716. The user display 426 isembodied as a small display screen 718. The ON/OFF switch 712 turns thepower to the interface unit 14 on and off. The up and down buttons 714and 716 are used to set and adjust one or more threshold levels and/orother parameters and settings. These thresholds and/or parameter may beutilized and/or forwarded to the sensor unit 12 to adjust a remote rainsensor to different threshold levels at the sensor unit 12 of the rainsensor system 10, such as described in U.S. Pat. No. 6,570,109; however,the threshold level is set electronically and at the interface unit 14.For example, by pressing the buttons 714 and 716, the user switchesbetween multiple discrete levels of rain thresholds, e.g., a lowthreshold, a mid threshold and a high threshold. In other embodiments,the up and down buttons 714, 716 cause an up and down gradient or analogadjustment to the stored threshold level. The display 718 may beconfigured to indicate which threshold level the interface unit 14 iscurrently set, notify the user of battery strength or low battery,indicate if the interface unit 14 is in watering interrupt mode or not,and other such information. In some embodiments, the display screen 718is not included.

In other embodiments, such as shown in FIG. 7B, an additional selectionbutton 715 is provided that allows a user to select different adjustablefeatures or settings of the interface unit 14. For example, theselection button 715 provides different adjustment functionality tobuttons 714 and 716. The display 718 indicates what parameter or settingthe user may adjust with buttons 714 and 716. For example, by repeatedlypressing the selection or menu button 715, the user may navigate betweendifferent selectable or adjustable settings or features. For example, asdescribed above, the selection button 715 allows the user to makeadjustments to the rain fall threshold level. Pressing the button 715again may allow the user to change the rain delay period after the waterthreshold has been exceeded and returned back below the threshold, tochange the temperature threshold level, and/or change other parametersor settings. The button 715 may also allow features to be turned on oroff with the buttons 714 and 716. For example, button 714 may be used toturn a feature selected by button 715 on, while button 716 turns thatfeature off.

Referring to FIG. 8, in some embodiments of the interface unit 14, thethreshold level is set by moving a multi-position switch 812 or othertype of drag bar between multiple positions. Each switch positionelectrically signals to the processor what threshold level correspondsto the proper switch position. In many embodiments, precipitationamounts between, for example, ⅛″ to ¾″ are selectable in discreteincrements or continuous manner. Further, in some embodiments, the userinput 424 comprises a three-position toggle switch 814 to allow the userto configure the unit for the desired operation. The switch 814 has acenter, left and right position. In some embodiments, placing the switchinto the center position places the interface unit 14 into a normaloperational mode where irrigation is inhibited if sufficientprecipitation has been detected by the sensor unit 12. Placing theswitch into the left position places the interface unit 14 into a bypassmode where irrigation is not inhibited by the system. The setting theswitch into the right position places the interface unit 14 into a testmode. In some embodiments, the right position is a spring-loaded returnto center, automatically releasing to center position e.g., normal mode,when the switch is no longer held in position. The user display 426, insome embodiments, may include an LCD backlit display screen 816. In manyembodiments, the user input 424 may further include a pushbutton switch820 to allow the user to activate the LCD backlight for a period oftime.

FIG. 29A is an illustration of alternate embodiment of the interfaceunit 14. This embodiment comprises for example an LCD touch screenembodying both user input and user display functionality. In otherembodiments, the user input may comprise selectable buttons, dialsand/or switches, and the user display may be a graphical display and/orother means of displaying data to the user. The user input 424 isembodied as including a rain threshold selector 2936, a temperaturethreshold selector 2926, rain sensor activation selector 2932 andtemperature activation selector 2930. The rain threshold selector 2936and temperature threshold selector 2926 enable the user to set or adjustthe threshold level for the amount of rain or temperature respectively.These thresholds may be utilized at the interface unit 14 for makingdecisions regarding whether to inhibit/interrupt or permit/allowirrigation, and/or may be forwarded to the sensor unit 12 to adjust aremote rain senor to different threshold levels at the sensor unit 12.The rain activation selector 2932 and the temperature activationselector 2930 further allow the user to adjust the mode of operationwherein the user may select to inhibit irrigation based on the amount ofrain or precipitation and/or the temperature. For example, using theselectors 2930 and 2932 the user may chose to interrupt irrigation basedon both precipitation and temperature data by activating both selectorand/or one or neither of the measurements by deactivating either or bothof the selectors 2930 and 2932. It is noted that the rain thresholdselector 2936 and the temperature threshold selector 2926 may begenerically referred to as selectable inputs that allows a user toadjust a respective threshold level.

The display 2900, as illustrated in FIG. 29A, is embodied as aconnectivity indicator 2938, a signal strength indicator 2920, aconnection indicator 2924, a rain indicator 2934, a battery strengthindicator 2922, a temperature indicator 2928, and a system statusindicator 2940. The connectivity indicator 2938 indicates whether thereis a connection between the interface unit 14 and the sensor unit 12.The signal strength indicator 2920 displays the signal strength of thewireless connection between the sensor unit 12 and the interface unit14, where the number of bars represents the strength of the signalsreceived from the sensor unit 12 at the interface unit 14. Theconnection indicator 2924 displays the number of sensor units 12currently connected to the interface unit 14 and further displays whichof the sensors 12 a-n is currently able to communicate with theinterface unit. For example, two sensor units are illustrated, the upperleft one in active communication with the interface unit, while thelower left one is not connected to the interface unit. The rain fallindicator 2934 and the temperature indicator 2928 display the amount ofrain fall and the temperature currently present at the sensor unit 12relative to the thresholds (indicated by 2936 and 2926). The signalstrength indicator 2920 displays the signal strength between theinterface unit 14 and the sensor unit 12. The battery strength indicator2922 may display the battery strength of the battery at the interfaceunit, sensor unit, and/or the rain sensor system 10 as a whole. Forexample, in one embodiment, the battery strength indicator displays thebattery strength measurement that it receives from the sensor unit. Thesystem status indicator 2940 displays the mode of operation, i.e.,whether the system inhibits irrigation based on rain fall, temperature,and/or both, and additionally displays whether irrigation is inhibitedcurrently.

As illustrated in FIG. 29A, the top section of the system statusindicator 2940 indicates whether the system is controlling irrigationbased on the measurement of rain, temperature, or both. For example,FIG. 29A shows the system status indicator displaying that the system iscurrently only inhibiting based on the amount of rain, i.e., only therain symbol is present at the top of the indicator. The system statusindicator further indicates whether the system is currently interruptingirrigation, where the sprinkler symbol on the indicator is eithershowing irrigation or displays that no irrigation is occurring, forexample, the system status indicator as illustrated in FIG. 29Aindicates that irrigation is currently not interrupted since thesprinkler symbol is showing irrigation.

FIG. 29B illustrates an alternative embodiment 2901 of the display 2900of the interface unit 14 for use with the system 10, for example inembodiments when the interface unit 14 is coupled with multiple sensorunits. As illustrated, in some embodiments the connection indicator 2924displays the interface unit, and also displays multiple sensor unitscoupled to the interface unit (in this case sensor units 1, 2, 3 and 4).The interface unit also displays signal strength 2920, and batterystrength 2922 for each of the sensor units 12.

With respect to the embodiments of FIGS. 7A, 7B, 8, 29A and 29B andothers described herein, prevention of tampering of slide switchesand/or push buttons may be provided by using a mechanical cover (notshown) over the switches/buttons. Additionally or alternatively, in someembodiments, buttons have to be pressed and held for a period of time(e.g., 2-5 seconds) before any changes occurs. This prevents theaccidental altering of receiver unit settings.

The interface unit 14 may be powered by connection to the controller 30,e.g., it draws power from the 24 VAC power source of the controller 30.In other embodiments, battery, solar, wind powered or other powersources and/or combinations of sources may be used to supply power tothe interface unit 14.

In some embodiments, the sensor unit 12 includes an indicator light,such as a bi-color LED, that is visible to a user and also includes thedriver circuitry and power to drive the indicator light. This indicatorlight is useful when initializing the sensor unit 12 and/or theinterface unit 14. For example, in some embodiments, the interface unit14 includes a test mode button that when pressed sends a signal to thesensor unit 12. In one embodiment, when the sensor unit 12 receives thesignal, it illuminates the indicator light. An installer may mount thesensor unit 12 to a given location. The test button on the interfaceunit may be activated allowing the installer to return to the sensorunit to verify that the indicator light is illuminated, verifying thatthe communication between the sensor unit 12 and the interface unit 14is valid.

In some embodiments, additionally or alternatively, when the sensor unitreceives the signal from the interface unit it determines the signalstrength of the signal and displays the signal via the indicator light.For example, in one embodiment the indicator light blinks a certainnumber of times representing the signal strength of the test signal. Aninstaller may use the signal strength indication to locate one of aplurality of possible installation locations with the best signalstrength. Additionally, in some embodiments the installer may move thesensor unit where the signal strength varies with the change inlocation, and further where the determining and displaying of the signalstrength is done automatically, so that the installer may install theinterface unit, push the test message and then move the sensor unit inthe remote location until the installer finds a location with the bestsignal strength where the sensor unit 12 may be installed.

Additionally and/or alternatively, once power is applied to theinterface unit 14, the interface unit starts sending signals to thesensor unit 12 for a period of time. If the sensor unit 12 is in range,the indicator light is illuminated. For example, an installer maydetermine whether the location of the sensor unit 12 is adequate and/orin communication with the interface unit 14 based on the decisioncriteria of whether the bi-color LED is illuminated (e.g., illuminatedgreen). If the location is determined to be inadequate, the bi-color LEDis not illuminated or is illuminated a second color (e.g., illuminatedred).

FIG. 9 illustrates a flow chart of the process 900 by which theinterface unit communicates with the sensor unit once communication isestablished between the interface unit 14 and the sensor unit 12,according to some embodiments of the rain sensor system 10 illustratedin FIGS. 1 and 2. In some embodiments, the process 900 initiates at step910 where a determination is made as to whether there is a sensor unit12 to receive an activation and/or start up message from the interfaceunit. This determination may include retrieving from memory 418identification information for one or more sensor units 12 with whichthe interface unit is associated. Step 910 may be an optional step. Forexample, when there is only a single sensor unit 12 that is associatedwith the interface unit. Additionally or alternatively, the interfaceunit may instead skip to step 912 and broadcast a request as describedbelow to each sensor unit associated with the interface unit 14. Thisidentification information may include the version number of the sensorunit, an identification number of the sensor unit and/or otherinformation uniquely assigned to the sensor unit. Further, thisinformation, in some instances, is stored in the memory 418 at the timethe sensor unit 12 is installed, or assigned to an interface unit 14. Ifthere are no sensor units associated with the interface unit, theprocess 900 moves to step 920 where a message is displayed on the userdisplay 426 alerting the user that there are no sensor units 12associated with the interface unit 14.

In step 912, once power is applied to the interface unit 14 theinterface unit enters an initialization mode and transmits a request toone or more sensor units 12. In step 914, the interface unit 14 checksto see if an acknowledgment message is received from the sensor unit 12.When an acknowledgment is received in step 914 the process thencontinues to step 916, where the interface unit 14 processes the messageand displays the appropriate data on the display 426 (e.g., aconfirmation of connection message, an identification of the one or moresensors from which responses are received and/or other suchinformation). When the sensor unit 12 is in range, as introduced above,the indicator light may also be illuminated at the sensor unit.

If it is determined in step 914 that an acknowledgment is not received,the process continues to step 918 where an incremental counter isincreased by one, and it is determined whether the request signal hasbeen transmitted a predefined number of times. If the request has notbeen sent the predefined number of times, the process returns to step912 to again transmit the request. The subsequent transmission may bedelayed for a period of time and/or the subsequent request may betransmitted at a higher transmit power in attempts to connect with thesensor unit 12. Alternatively, when an acknowledgment is not receivedafter a predetermined number of connection attempts the processcontinues to step 920 where it displays a message alerting the user.

Following step 916, following the initialization mode, the interfaceunit 14 enters the normal or sleep mode. In normal mode the interfaceunit will function in accordance with the process as described in FIG.6. In many embodiments, the interface unit 14 also provides a test modeto enable the user to determine whether or not a proposed location forthe sensor unit will result in satisfactory signal reception andcommunications reliability. This is made possible, in such embodiments,by having a two way communication between the sensor and interface unit.In the test mode, the interface unit 14 initiates a test messagetransmitted to the sensor unit and receiving an acknowledgment to verifythat the sensor unit 12 and interface unit 14 may communicate. The testmode may be initiated automatically by the system in the initializationstep. In some embodiments, the user may also initiate a test mode byusing the user input 424.

In many embodiments message traffic between the interface unit 14 andsensor unit 12 occurs in pairs, e.g., when a message is sent, there isan acknowledgement. In the event that the sender of an initial messagedoes not receive an acknowledgement corresponding to the message sent,the originator of the message may assume that the message was lost andattempt to retransmit the message. FIG. 10 illustrates a process 1000that is implemented in the event that loss of communication occursbetween the sensor unit 12 and interface unit 14 of rain sensor deviceor system 10 illustrated in FIGS. 1 and 2. In step 1010 after sending amessage, the originator of the message, e.g., the sensor unit 12 or theinterface unit 14, determines whether an acknowledgment is received.When an acknowledgement is received, the process 1000 continues to step1050 to continue normal operations. Alternatively, if an acknowledgmentis not received, typically within a predefined period of time, then theprocess continues to step 1012 where the originator resends the message.

In step 1014 the originator checks to see if an acknowledgment isreceived. When it is determined in step 1014 that an acknowledgment isreceived, the process continues to step 1050 and resumes its normaloperation. If no acknowledgment is received then the process continuesto step 1016 to determine whether a predefined time limit forreattempting to send the message is reached and/or whether the messageis retransmitted a predefined number of times. When it is determined instep 1016 that the predefined time period and/or number of attempts isnot reached, the process returns to step 1012 to continue attempting totransmit the message. Alternatively, when, an acknowledgment is notreceived within the predetermined period of time and/or within thelimited number of attempts, the system continues onto step 1018 wherethe originator attempts to determine whether there is interference inthe communications channel.

In some embodiments, both the sensor unit 12 and interface unit 14periodically monitor the RSSI values obtained from the receiver and/ortransceiver 316, 412 during periods where no message traffic is beingpassed. These values are noted and stored in memory so that informationabout the noise levels at the sensor unit 12 and interface unit 14locations are available with which to assess the communications channelat a given time. In some embodiments, when no message traffic is beingpassed, the interface unit 14 samples the RSSI value randomly, atscheduled times, at intervals, e.g., at intervals of one minute, or thelike. Additionally or alternatively, the sensor unit 12 may samples theRSSI value, randomly, at scheduled times or at intervals, e.g., atintervals of one hour. In step 1018 the originator of the message maysamples the RSSI value, for example from its receiver chip, and assesseswhether or not there is interference or noise levels that exceed limits.When it is determined that high noise level is present the systemcontinues to step 1020 where the originator increases the transmittalpower.

In step 1022, the device attempts retransmission of the message at theincreased transmitter power. In some embodiments, this step comprisesretrieving the maximum transmittal power from memory. In step 1024 thesystem checks to see if an acknowledgment is received. When anacknowledgement is received, the process continues to step 1050 totransition to a normal mode of operation. If the retransmission attemptdoes not result in an acknowledgment, step 1026 is entered where it isdetermined whether the noise level has returned to or is below athreshold and/or a nominal value. In some embodiments, the process mayrepeat steps 1022 and 1024 in attempts to resend the message for acertain period of time or a predetermined number of attempts beforecontinuing to step 1026. When it is determined in step 1026 that thenoise level over the communication link has subsided or reduced todesired levels, the process returns to step 1012 to retransmit themessage. In some embodiments when returning to step 1012 the interfaceunit sends a message to reset the transmittal power of the sensor unit.

Alternatively, when it is determined in step 1026 that the noise levelhas not reduced, the originator device continues to sample RSSI values,e.g., at predetermine time intervals and the process then proceeds tostep 1030. In step 1030, it is determined whether a period of time haselapsed without detecting a reduction in noise level (e.g., reduction toa desired level). If the time limit has not elapsed the process returnsto step 1026 to determine whether there has been a reduction in noiseover the channel. Alternatively, when the time period has elapsed, theprocess enters step 1032 where an error message is displayed and/orotherwise indicated and the process terminates. In some embodiments,during this process the user display 426 of the interface unit 14displays status information, such as a noise message or levels, errormessage, acknowledgement not received and/or other such information.

Returning to step 1018, when it is determined that the noise level isnot in excess, it is presumed that the receiving device at the other endof the communication channel (e.g., wireless link) has failed. Thesystem then continues to step 1040 where the transmitting deviceattempts to reestablish communication. In step 1042, it is determinedwhether an acknowledgement is received for the reconnection. When thereconnection is achieved, the process 1000 returns to step 1012 toresend the message (or in some instances to step 1050 for normaloperation). Alternatively, the process continues to step 1044, where itis determined whether a time limit has expired while attempting toreestablish communication. When the time limit has not been reached theprocess returns to step 1040. When the time limit has been reached, theprocess continues to step 1032, and an error message is displayed and/orotherwise indicated and the process terminates.

In some embodiments, the sensor unit 12 in performing steps 1016, 1030and/or 1044 may attempt implement a shorter amount of time and/or numberof tries before ceasing to transmit, and waits until the interface unit14 attempts to reconnect. Additionally or alternatively, the sensor unit12 may not perform all of the steps of the process 1000, and maytermination communication earlier in the process to await communicationfrom the interface unit 14. In some embodiments, the user display 426 ofthe interface unit 14 displays a NO SIGNAL message or other indicatorduring the time the interface unit is waiting for an acknowledgementand/or is attempting to reconnect until reconnection is achieved or theprocess terminates.

The next several figures illustrate and describe various types ofsensors and circuitry for sensing or generating a signal indicative ofthe amount of rain fall. These drawings have been simplified and do notillustrate all components of the device. For example, all components ofthe circuitry and outputs such as a power source (battery and/or solarcell) and wireless transmitters are not illustrated. Depending on theembodiment, a signal representing a sensed value that corresponds to anamount of rain fall received is transmitted to the interface unit 14. Insome forms, the interface unit is configured to properly interpret theinformation in the signal and correlate that information to acorresponding level of rain fall received. In other embodiments, thesignal is converted to a corresponding level of rain fall prior to beingtransmitted to the interface unit 14. Still further in someimplementations, the sensor unit 12 determines whether a threshold levelof rain is received and transmits an indication of whether the thresholdis exceeded in response to an inquiry from the interface unit 14.

Referring next to FIG. 11, a diagram is shown of a sensor unit 1102 foruse in a system to interrupt execution of one or more watering schedulesof an irrigation controller according to several embodiments. In thisembodiment, the sensor unit 1102 includes a housing 1104 having anopening 1106 to allow rain fall to enter a volume 1108. Although notillustrated, a ceramic or other porous filter is located in the opening1106 to allow rainfall to be received into the volume 1108 whilepreventing dirt and other debris from entering the volume. Within thevolume 1108 is a moisture absorptive material that expands and contractsbased on the presence of and absence of rain fall, such as a hygroscopicmaterial 1110 comprising a plurality of hygroscopic discs. It isunderstood that the shape and configuration of the hygroscopic materialmay vary according to the specific implementation. For example, thehygroscopic material 1110 may comprise discs (as illustrated, or maycomprise other suitable materials, such as an expandable granularmaterial (e.g., polyacrylamide, etc.) contained within an envelope orflexible container.

The material 1110 expands in the presence of water, expanding further asthe presence of water increases, and contracting as water is evaporatedfrom the volume 1108. Vents (not illustrated) are provided to allowevaporation, i.e., allow the volume 1108 to dry when rainfall is notpresent. A plunger 1112 is coupled to the material 1110 and a spring1114 to bias the material 1110 upwardly. A metal piece 1116 (e.g., ametal plate or short section of metal cylindrical tubing) is mounted onthe lower surface of the mechanical plunger 1112. This metal piece 1116is situated in proximity to a capacitor 1118 mounted on the printedcircuit board 1120 comprising the sensor electronics. In someembodiments, the printed circuit board 1120 may comprise a controller,memory, transceiver and/or other relevant elements. The capacitor 1118forms the capacitive arm of an oscillator. The capacitor 1118 is suchthat the electric field surrounding its plates should have sufficientextent so that the metal piece 1116 mounted on the plunger 1112 willaffect its capacitance. Expansion of the hygroscopic material 1110causes the spacing between the piece of metal 1116 and the capacitor1118 to change, altering the capacitance of the plunger/capacitorsystem. Changes in the capacitance of the system will result in a changeof the frequency of oscillation of the oscillator, the frequency ofcorresponding to the amount of precipitation. The sensed frequencyprovides an analog continuous measurement corresponding to the amount ofrain fall. The value of this sensed frequency is transmitted to theinterface unit for a determination of whether a rain threshold has beenexceeded. Additionally or alternatively in some embodiments, the rainsensor unit 1102 detects when a threshold amount of water is received.For example, contact of the piece of metal 1116 with the capacitor 1118or circuit board 1120 causes the closing of a switch indicating that athreshold amount of water has been exceeded such that a signalindicating that the threshold has been exceeded is then forwarded to theinterface unit in response to the request from the interface unit. Inanother embodiment, item 1118 is a mechanical switch or button that whencontacted by item 1116, presses the switch. In this embodiment, the factthat the switch is pressed, closed or contacted indicates to theelectronics that the threshold has been exceeded.

Referring next to FIG. 12, a sensor unit 1202 includes a strain gauge1204 coupled to the printed circuit board 1120 and that engages theplunger 1112 when the material 1110 expands. Expansion of the material1110 changes the force applied to the strain gauge 1204 by the plunger1112. The plunger 1112 may initially contact the strain gauge 1204 ornot and a spring 1114 may optionally be included between the straingauge 1204 and the plunger 1112. This change in force on the straingauge 1204 is detected by appropriate electronics on the printed circuitboard 1120. The sensed force provides an analog continuous measurementcorresponding to the amount of rain fall. The value of this sensed forceis transmitted to the interface unit 14 for a determination of whether arain threshold has been exceeded and/or a determination of whether athreshold is exceeded may be transmitted to the interface unit 14.

Referring next to FIG. 13, a sensor unit 1302 includes an inductor 1304wrapping around the material 1110 and coupled to the printed circuitboard 1120. The inductor 1304 is fabricated from a fine wire and formsone arm of an oscillator circuit on the circuit board 1120. Expansion ofthe hygroscopic discs (material 1110) changes the inductance andinternal dissipation of the inductor, changing the frequency andamplitude of the oscillator. This change is detected by appropriateelectronics on the printed circuit board 1120, providing an analogcontinuous measurement corresponding to the amount of rain fall and/oran indication of exceeding a threshold. The value of this sensedfrequency and/or amplitude is transmitted to the interface unit 14 for adetermination of whether a rain threshold has been exceeded.

Referring next to FIG. 14, a sensor unit 1402 includes graphite stackresistor 1404 coupled to the printed circuit board 1120 and that engagesthe plunger 1112 when the material 1110 expands. Expansion of thehygroscopic discs (material 1110) changes the force applied to thegraphite stack resistor 1404 by the plunger 1112. The plunger 1112 mayinitially contact the stack resistor 1404 or not and a spring 1114 mayoptionally be included between the stack resistor 1404 and the plunger1112. This change in force on the graphite stack 1404 changes itselectrical resistance, and is detected by appropriate electronics on theprinted circuit board 1120, providing an analog continuous measurementcorresponding to the amount of rain fall. The value of this sensedresistance is transmitted to the interface unit 14 for a determinationof whether a rain threshold has been exceeded.

Referring next to FIG. 15, a sensor unit 1502 includes a magnet 1504 ona surface of the mechanical plunger 1112. This magnet 1504 is situatedin close proximity to a Hall Effect device 1506 mounted on the printedcircuit board 1120 comprising the circuitry or electronics of the sensorunit 1502. Expansion of the hygroscopic discs (material 1110) causes thespacing between the magnet 1504 and the Hall Effect device 1506 tochange, changing the output of the Hall Effect device 1506. This changein the output of the Hall effect device 1506 is detected by appropriateelectronics on the printed circuit board 1120, providing an analogcontinuous measurement corresponding to the amount of rain fall. Thevalue of this output is transmitted to the interface unit 14 for adetermination of whether a rain threshold has been exceeded.

Referring next to FIG. 16, a sensor unit 1602 is shown in which the baseof the mechanical plunger 1112 is in contact with a wiper 1604 of afixed resistive sensing element 1606. In some embodiments, the resistiveelement and the wiper form a linear potentiometer. Expansion of thehygroscopic discs (material 1110) changes the position of the linearwiper 1604 on the potentiometer 1606, changing its resistance. Thischange in resistance is detected by appropriate electronics on theprinted circuit board 1120, providing an analog continuous measurementcorresponding to the amount of rain fall. The value of this resistanceis transmitted to the interface unit 14 for a determination of whether arain threshold has been exceeded.

Referring next to FIG. 17, a sensor unit 1702 is shown which does notuse a hygroscopic material, and instead uses a capacitor 1704 includinga set of plates or electrodes. In the illustrated form, the electrodesare formed as coaxially aligned cylindrical tube electrodes 1706 and1708, electrode 1706 being the outer coaxial tube and electrode 1708being the inner coaxial tube. These tubes are illustrated in crosssection view. The capacitor 1702 forms the capacitive arm of anoscillator implemented on the circuit board 1120. The volume 1108 andelectrodes 1706 and 1708 are configured such that water collects in thespace between the electrodes 1706, 1708, changing the capacitance of thecoaxial system. The high dielectric constant of water will effect alarge change in the capacitance of the system under conditions of smallaccumulations of precipitation. Changes in the capacitance of the systemwill result in a change of the frequency of oscillation, providing ananalog continuous measurement corresponding to the amount of rain fall.The value of this changing frequency is transmitted to the interfaceunit 14 for a determination of whether a rain threshold has beenexceeded.

Referring next to FIG. 18, a sensor unit 1802 is shown which does notuse a hygroscopic material. In this embodiment, a material whoseelectrical resistance changes when exposed to water is employed todetect precipitation. As illustrated, a resistance cell 1804 is locatedwithin the volume 1108. Electrodes 1806 and 1808 couple from theresistance cell 1804 to the circuit board 1120 and measure theresistance across the cell. Resistance across the resistance cell 1804decreases as it becomes wet relative to the initial readings when thesensor unit is initialized. Changes in the resistance of the cell 1804correspond to changes in the level of rain fall received, providing ananalog continuous measurement corresponding to the amount of rain fall.The value of this changing resistance is transmitted to the interfaceunit 14 for a determination of whether a rain threshold has beenexceeded.

Referring next to FIG. 19, a sensor unit 1902 is shown in which the baseof the mechanical plunger 1112 is in contact with a ferrous plunger1906. This plunger 1906 is situated such that it moves within aninductive coil 1908 connected to the printed circuit board 1120. Theinductor 1908 is fabricated from a fine wire and forms one arm of anoscillator circuit on the circuit board 1120. Expansion of thehygroscopic discs (material 1110) changes the position of the plunger1906 altering the inductance of the plunger/inductor system. Changes inthe inductance of the system will result in a change of the frequency ofoscillation of the oscillator. This frequency change is detected byappropriate electronics on the printed circuit board 1120, providing ananalog continuous measurement corresponding to the amount of rain fall.The value of this frequency is transmitted to the interface unit 14 fora determination of whether a rain threshold has been exceeded.

Referring next to FIGS. 27A and 27B, a sensor unit 2700 is shown inwhich the mechanical plunger 1112 is in contact with the wiper 1604 ofthe fixed resistive sensing element 1606. As illustrated in FIG. 27B, inone embodiment a spring 2712 is coupled to the wiper 1604 and theplunger 1112 pushes the wiper towards the resistive sensing materialmaintaining appropriate contact between the resistive sensing materialand the wiper. In some embodiments the wiper and the resistive sensingelement are parts of a linear potentiometer. Expansion of thehygroscopic discs (material 1110) changes the position of the linearwiper 1604 on the resistive sensing element 1606, changing itsresistance. In some embodiments, this change in resistance is detectedby appropriate electronics on the printed circuit board 1120, where itis processed to generate an indication representing an amount of rainfall. For example, in one embodiment, the processing results in ananalog continuous measurement corresponding to the amount of rain fall.The indication representing the amount of rain fall derived from thisresistance is transmitted to the interface unit 14 for a determinationof whether irrigation should be permitted or interrupted. In someembodiments, the indication may also be used by the sensor unit todetermine whether some internal criteria are met, for example, whenchanging the mode of operation of the sensor unit. In someimplementations, the sensor unit also includes an antenna 2704, a lightindicator 2706 and a temperature sensor 2708 coupled to the printedcircuit board. Further, in some embodiments, the sensor unit comprises abattery housing 2710 which holds the batteries from which the sensorunit draws its power.

According to several embodiments, the wiper 1604 can be genericallyreferred to as a first element, while the resistive sensing element 1606may be generically referred to as a second element. In a preferredembodiment, the first element is a moving element and the second elementis fixed in a location. Generically, the plunger causes the firstelement to move relative to the second element causing a change in avariable (in this case, an electrical resistance) corresponding to anamount of rain fall. In some embodiments, the controller implemented onthe circuit board is measures the variable and generates signalscomprising an indication of the amount of rain fall based on themeasured variable.

Referring next to FIG. 28, a sensor unit 2800 is shown in which themechanical plunger 1112 is in contact with a first electrode 2804 (e.g.,an electrode plate). In response to expansion/contraction of thehygroscopic disks, the moving plunger moves the first electrode 2804relative to a second electrode 2808 (e.g., an electrode plate) fixed tothe electronic circuit board 1120. The fixed second electrode 2808 iscovered with a layer of insulator material 2806, e.g., Mylar insulation,where the insulator material is in contact with the moving firstelectrode 2804 such that it maintains a gap between the fixed electrode2808 and the moving electrode 2804. As illustrated in FIG. 8, in oneembodiment, a spring 2810 coupled to the fixed electrode 2804 and theplunger 1112 pushes the moving electrode 2804 towards the fixedelectrode 2808 and the insulator material maintaining appropriatecontact between the fixed electrode covered with the insulator materialand the moving electrode. Expansion of the hygroscopic discs (moistureabsorptive material 1110) changes the position of the moving electrode2804 relative to the fixed electrode 2808, changing the surface area ofthe fixed electrode 2808 that is covered by the moving electrode 2804.Accordingly, this changes the capacitance generated between the twoelectrodes given a voltage difference therebetween. For example, avoltage is applied to the fixed electrode. In some embodiments, thischange in capacitance is detected by appropriate electronics on theprinted circuit board 1120, where it is processed to generate anindication representing an amount of rain fall. For example, in oneembodiment, the processing results in an analog continuous measurementcorresponding to the amount of rain fall. The indication representingthe amount of rain fall derived from this capacitance is transmitted tothe interface unit 14 for a determination of whether irrigation shouldbe permitted or interrupted. In some embodiments, the indication mayalso be used by the sensor unit to determine whether some internalcriteria are met, for example, when changing the mode of operation ofthe sensor unit.

According to several embodiments, the first electrode 1806 can begenerically referred to as a first element, while the second electrode1808 may be generically referred to as a second element. In a preferredembodiment, the first element is a moving element and the second elementis fixed in a location. Generically, the plunger causes the firstelement to move relative to the second element causing a change in avariable (in this case, an electrical capacitance due to a changingsurface area of the first element positioned above the second element)corresponding to an amount of rain fall. In some embodiments, thecontroller implemented on the circuit board is measures the variable andgenerates signals comprising an indication of the amount of rain fallbased on the measured variable.

In many embodiments, the rain sensor system 10 is capable of measuringrainfall and according to one or more selected settings to permit orprevent an irrigation controller 30 from irrigating. Rainfall settingsare, for example, from ⅛″ to ¾″ and are selectable at the interface unit14. The rain sensor system 10 comprises the remote sensor unit 12, andan interface unit 14 mounted near an irrigation controller 30.Communication between the remote sensor unit 12 and interface unit 14,according to some embodiments, is a two way wireless radio link that mayeliminate the need to route wires/cable between the units. The wirelesssensor unit 12 may be in one of the following forms or a combinationsthereof, a wireless rain sensor (transmitter/receiver combination pack),a wireless rain/freeze sensor (transmitter/receiver combination pack), awireless rain sensor receiver, a wireless rain/freeze sensortransmitter, and/or a wireless rain/freeze sensor receiver.

FIG. 31 illustrates one possible implementation of the overall operationof the system 10 according to several embodiments. In step 3112 thesensor unit 12 generates an indication of the amount of rain and/orother data such as temperature. In one embodiment, the rain sensorgenerates such data periodically e.g. every 5 minutes. In otherembodiments, the sensor unit may generate such indications in responseto a request from the interface unit 14. Next, in step 3114 the sensorunit transmits a signal comprising at least the generated indication tothe interface unit 14. In some embodiments, the sensor unit may initiatetransmission to the interface unit 14 once it detects a change in someatmospheric parameters, e.g., amount of rain fall and/or temperature,and sends an update message to the interface unit. Additionally oralternatively, the sensor unit 12 may transmit the indication to theinterface unit 14 at fixed intervals, e.g. every 6 hours. The sensorunit may also transmit the indication to the interface unit 14 inresponse to a request from the interface unit 14. In one embodiment, themessage may include the sensed amount of rain fall, sensed temperature,battery strength, signal strength and/or other data available at thesensor unit.

In step 3116, the interface unit 14 receives the signal containing thedata from the sensor unit. In step 3118, the signal is processed toobtain the indication of data from the sensor unit, such as amount ofrain or precipitation, and/or temperature. Next, in step 3120 theinterface unit 14 determines whether a relationship exists between theindications and a threshold and/or other criteria. If in step 3120 theinterface unit 14 determines that the relationship exists, then in step3122 the interface unit generates an interrupt command to causeirrigation executed by an irrigation controller to be interrupted.Alternatively, when the interface unit 14 determines that therelationship does not exist, the interface unit 14 does not take anyactions and returns to step 3116. Thus, in this way, the interface unitallows or permits irrigation executed by the irrigation controller tooccur. In some embodiments, steps 3118 and 3120 may be generically bereferred to as the step of determining, based at least on the indicationfrom the signal, whether irrigation should be interrupted.

The interface unit 14 typically is mounted on a wall near to, and wiredto, an irrigation controller 30. The interface unit may include methodsfor outdoor and/or indoor mounting. For example, a mounting plate may beprovided to be secured into position with one or more screws. Theinterface unit 14 then slips and/or otherwise is connected onto themounting plate. Further, the interface unit 14 typically includes ahousing. The housing may be made of plastic and may include means tosecure the device to a wall without the mounting plate (e.g., a pair ofkeyhole slots). The housing may be made of polymetric material. It isdesired that if the external housing is of a polymetric material, itmeets UL standards for flammability, UL 94-5V or better, UV resistance,water absorption, and other applicable UL safety standards. The housingis set up for outdoor/indoor mounting.

An installation mode is activated in the interface unit 14 that thesensor unit 12 unit responds to by displaying the signal strengthreceived from the interface unit. The sensor unit 12 may be mounted withone or more attached brackets in a location that indicates good signaland that catches direct rainfall. The mounting bracket employed by thesensor unit 12 is designed so that a minimum number of tools are neededfor installation. The material employed for this bracket is light inweight and resistant to corrosion from water and sunlight.

After installation a simple signal test may be performed to verifycommunication is working properly between the sensor unit 12 and theinterface unit 14. In some embodiments, the sensor unit 12 has batteriesthat last for 5 years or more under the following conditions: one (1)“TEST” mode activation per year for the duration of five minutes and atotal of ten (10) one-second transmissions per day at a power level of+10 dBm. According to many implementations, the system does not requireend-user calibration. Normal maintenance consists of debris removal,elimination of plant encroachment, and periodic battery replacement.

The rain sensor system 10 is used in conjunction with 24 VAC irrigationcontrollers 30 to conserve water usage by automatically preventing theirrigation controller from irrigating once the rainfall reaches apre-set level.

In some embodiments, the interface unit 14 operates by receivingperiodic communication from the sensor unit and processing the datareceived to decide whether or not to irrigate based on internal rulesincluding, for example, past history, rate of rainfall, thresholds,and/or other criteria. Additionally or alternatively, in someembodiments, the interface unit 14 may operate by interrogating thesensor unit 12 and then deciding to water or not water based on internalrules including past history. In some situations, for example, thesensor unit 12 will show dry conditions and the interface unit 14 willnot allow watering due to recent rainfall. Watering may be prevented bybreaking the continuity of the common circuit or connecting to thesensor input of the irrigation system, which prevents the solenoidvalves of the irrigation system from operating.

In some embodiments, the system operates in either the 868 MHz or 915MHz license-free ISM bands. It is understood other embodiments willoperate in other frequency bands, for example, some embodiments operateat 2.4 GHz and others operate in the 400 MHz ISM band. The systemoperates reliably at a straight-line distance of 300 feet or more withthe sensor unit 12 installed ten feet above the ground and the interfaceunit 14 installed five feet above the ground.

In one example implementation of the rain sensor device or system 10,communications reliability is defined as a message reception rate of 99%or more between the sensor unit 12 and the interface unit 14 while thesystem is situated in a residential environment with buildings, treesand other obstructions. This 99% reliability performance metric is withrespect to an environment where Rayleigh fading is present, having alink budget fading margin of 20 dB.

In the 915 MHz band the received signal strength profile that is used toapproximate the propagation environment over communication distancesless than the breakpoint distance is graphically illustrated in FIG. 20,with the breakpoint distance defined as 4h_(TX)h_(RX)/λ where h_(Tx) isthe transmitter height above ground, h_(RX) is the receiver height aboveground, and λ is wavelength. For the 868 MHz band, the received signalstrength profile used is graphically illustrated in FIG. 21.

The sensor unit 12 and interface unit 14 may each employ a low-cost,single chip radio transceiver device that is capable of operating acrossthe 868 MHz and/or 915 MHz ISM bands without requiring tuning orcomponent changes. The transceiver devices 316, 412 are capable ofgenerating either direct sequence or frequency hopping spread spectrumsignals. In some embodiments, it is desired that the transceiver devicemeets UL 1950 safety standard and CSA C22.2. In one embodiment, thedevices may have a maximum transmitted power level of 10 milliwatts (+10dBm) or more into a 50Ω resistive load. The frequency of operation andtransmitted power level are adjustable through firmware. The device iscapable of achieving compliance with all applicable FCC regulations forunintentional and intentional radiators in the 868 MHz and/or 915 MHzbands. In some embodiments, the transceiver 412 may be implemented as asingle-chip transceiver 412 employed on the sensor unit 12 providing ananalog and/or digital Received Signal Strength Indicator (RSSI) outputsignal. In one embodiment where the RSSI output is an analog signal, itis provided to one channel of the controller's ADC.

In many embodiments, the sensor unit 12 operates from a high capacitylithium-ion battery. It may employ power conservation techniques toprovide a battery lifetime of five years or more while meeting its otherfunctional operating capabilities. A voltage sensing or other batterymonitor circuit such as battery voltage sensor 320 is employed, in someembodiments, to measure the battery voltage while it is under load.According to some implementations, the output voltage signal of thismonitor circuit is provided to one channel of the controller's ADC 326.

In some embodiments, the sensor unit 12 may include an adjustablecap/collector, and a micro sensor on the PWB protected by a waterproofseal that measures rainfall total.

According to some implementations, the controller 312 of the sensor unit12 is implemented through and/or utilizes a low-cost 8-bitmicrocontroller that has sufficient computational power and speed tosupport the functional capabilities of the unit. It is equipped with oneor more very low power “sleep” modes capable of being terminated byexternally and/or internally-generated interrupt events. Themicrocontroller or microprocessor may employ a quartz crystal forgeneration of an internal clock signal.

In some embodiments, the controller 312 additionally employs FLASHmemory for storage of executable firmware, and is capable of beingprogrammed “in-system”. An in-system programming port may be availableon the printed circuit board for accomplishing the programming processduring final assembly. The in-system programming port may be accessiblevia surface pads (through the use of “pogo” pins on an ICT fixture). Aprogramming header may also be available on the printed circuit board topermit reprogramming the controller during firmware development. In someimplementations, Circuit boards may be designed for ease of testabilitysuch as using automated test fixture equipment.

Additionally the controller may include on-chip EEPROM for non-volatilestorage of miscellaneous data for support of its functionalcapabilities, according to some embodiments. On-chip RAM may also bepresent in sufficient quantity for the controller's functionalcapabilities. The controller may also include an on-chip ADC 326 with8-bit resolution or greater. In this and/or other implementations, theADC 326 contains four or more input channels.

In some embodiments, the sensor unit 12 includes a rain sensor 318employing hygroscopic material suitable for the detection ofprecipitation. This material typically has a useful lifetime around thatof the power source 324, about five years or more. Upon exposure toprecipitation, expansion of the hygroscopic material causes a change ina variable. This change in variable or a value derived from the changein the variable is provided to one channel of the controller's ADC 326.

The hygroscopic material and the mechanical structures designed tocontain it and translate its expansion to a linear displacement arecalibrated, in some embodiments. This calibration establishes theability of the structure to detect between about ⅛ and ¾ inches ofprecipitation with a repeatability of ±20% or better. Unit-to-unitvariations in the detection of identical amounts of precipitation are±20% or less.

In one embodiment, in order to detect ambient temperature, the sensorunit 12 may also employ a temperature-sensitive device 322 such as athermistor, temperature-dependent current source, and/or other suchdevice. For example, a “direct digital” temperature sensor may beemployed as the temperature sensor 322. According to some embodiments,the temperature-sensitive device 322 is capable of detecting an ambienttemperature of 37° F. with a tolerance of ±5% or better. In someembodiments, the output signal from the temperature-sensitive device isprovided to one channel of the controller's ADC.

In one or more embodiments, the sensor unit 12 is also equipped with alight indicator, such as a bi-color LED capable of illumination in redor green. The LED is visible through a clear window in the unit'splastic enclosure to eliminate the need to create a penetration throughthe plastic. The enclosure of the sensor unit 12 may also include amounting bracket for outdoor mounting of the sensor unit.

In some embodiments, when the power source 324 (e.g., battery) isinserted into the sensor unit 12, the unit powers up and enters“INITIALIZATION” operational mode. During the initialization mode thesensor may receive a signal from the interface unit 14 to establish awireless and/or wired communication path between the interface unit 14and the sensor unit 12. Alternatively, the sensor unit may initiate amessage to one or more interface units 14 and start the initializationprocess. Once the sensor unit 12 receives the set up signal from theinterface unit it will send back an acknowledge signal. In one or moreembodiments, the acknowledgment signal comprises identificationinformation and/or other local information. The interface unit 14 thenreceives the acknowledgment message. In one embodiment, the interfaceunit 14 extracts the ID information and/or other information from thesignal and may store the data onto memory 418. According to someimplementations, the interface unit 14 may use the data from the setupacknowledge signal in the future to validate communication from thesensor unit to ensue that it only responds to communication from thesensor units it is paired up with. Similarly, in some embodiments thesetup signal may comprise ID information about the interface unit 14which the sensor unit may retrieve and store in memory 314, for examplefor future validation of signals from the interface unit. Afterprocessing the acknowledgment signal at the interface unit 14 the sensorunit 12 and the interface unit 14 are paired up and may communicatethrough the wireless and/or wired communication link 15. In someembodiments, before sending an acknowledgment message the sensor unit 12will determine if certain criteria are met. For example in oneembodiment, the sensor unit 12 may determine whether there is user inputat the sensor unit and will only transmit the acknowledge message whenuser input is present at the sensor unit. For example, the sensor unitmay check to see if the plunger on the rain sensor unit is fullydepressed.

Additionally or alternatively, during this mode, the controller 312 maycomplete firmware initializations in order to set the unit up foroperation. In one embodiment, once firmware initializations arecompleted, the controller 312 reads the battery voltage under full load(with the exception of the radio transmitter or transceiver 316). If thebattery voltage is above a minimum voltage for proper operation in“NORMAL” mode, the sensor unit 12 transmits a signal, i.e. a BATTERY_OKmessage, to the interface unit 14. This signal may be transmitted at adefined power and/or transmitted utilizing the maximum transmitter poweravailable. The interface unit 14 may respond to receipt of this messageby sending an acknowledgement signal, i.e., a BATTERY_OK_ACKNOWLEDGEmessage back to the sensor unit 12. Upon receipt of this message, thesensor unit 12 enters a sleep or “NORMAL” operational mode.

Alternatively, if the measured battery voltage is below the minimumallowable voltage for proper operation in “NORMAL” mode, the unittransmits a low battery warning, e.g., a LOW_BATTERY_WARNING message, tothe interface unit 14. This message is transmitted at a defined powerand/or utilizing the maximum transmitter power available. The interfaceunit 14 responds to receipt of this message by sending anacknowledgment, e.g., a LOW_BATTERY_ACKNOWLEDGE message, back to thesensor unit 12. Upon receipt of this message, the sensor unit 12 enters“LOW BATTERY” operational mode.

In some embodiments, during “INITIALIZATION” mode the bi-color LED willilluminate in both red and green for a period of one second. Thisprovides a visual indication to the user that the unit has powered upand is operating. In other embodiments the light indicator may blink anumber of times displaying the signal and/or connection strength betweenthe sensor unit 12 and the interface unit 14.

In some embodiments, while the sensor unit 12 is in “NORMAL” mode, thecontroller 312 brings itself out of its low-power mode periodically toquery the sensors and/or other peripheral devices. In one or moreembodiments, the controller 312 will process the data to determine ifthere has been any change in the data obtained from the sensors and/orother devices, e.g., a change in temperature, change in the amount ofrain, etc. When the controller determines that a change has occurred, itwill initiate a transmission to the interface unit 14. Additionally oralternatively, in some embodiments, the sensor unit 12 will initiate atransmission to the interface periodically, at fixed intervals, sendingthe data received from the sensors. In this embodiment, the data may bequeried from the sensors at the time of the transmission or may beretrieved from memory 314. In an alternative embodiment, while in“NORMAL” mode, the sensor unit 12 typically will not initiate a radiotransmission to the interface unit 14. The sensor unit 12 will minimizeits power consumption to maximize its battery life, and will place itsradio receiver device into a “quasi-sleep” mode. In this embodiment,while in “quasi-sleep” mode, the radio receiver is capable of detectingthe presence of an incoming message but may accomplish this without theneed to apply full power to all receiver circuitry. In one or moreembodiments, during normal mode the bi-color LED may be extinguished.

At intervals, for example of approximately once per day, the controller312 brings itself out of its normal or sleep mode and activate one ormore and typically all peripheral systems on the unit (with theexception of the radio transmitter or transceiver 316). Once allperipherals have been activated, the controller 312 performs ameasurement of the full-load battery voltage. The resulting measurement,at least in some embodiments, is stored in memory 314 and/or transmittedto the interface unit 14. Additionally or alternatively, the resultingmeasurement may be compared with a non-volatile constant stored inmemory 314, i.e., EEPROM, to determine if the battery is nearing the endof its useful life. In order to accurately make this determination, thecontroller may also make a measurement of the ambient temperature tocalibrate the measured battery voltage. In some embodiments, if thefull-load battery voltage is below the minimum allowable voltage (end ofbattery life is approaching), the controller may switch the system into“LOW BATTERY” mode.

While in “Normal” mode the sensor unit 12 may respond to a number ofmessages from the interface unit 14. For example, the sensor unit 12responds to a SENSOR_STATUS_REQUEST message from the interface unit 14.Upon receipt of a SENSOR_STATUS_REQUEST message, the controllerinitiates a measurement of the hygroscopic material displacement,ambient temperature, and full-load battery voltage. After thesemeasurements have been completed, the sensor unit 12 constructs amessage packet containing the results of the measurements. It alsoincludes in the message packet the RSSI value observed during thereceipt of the SENSOR_STATUS_REQUEST message. The entire message packetis transmitted to the interface unit 14 in the form of a SENSOR_STATUSmessage.

The sensor unit 12 may also respond to a LINK_QUALITY_REQUEST messagefrom the interface unit 14. A LINK_QUALITY_REQUEST message instructs thesensor unit 12 to transmit a LINK_QUALITY message back to the interfaceunit 14 at the power level specified in the payload of theLINK_QUALITY_REQUEST. The LINK_QUALITY message contains data packetsthat indicate the requested power level for the transmission and theRSSI value observed during the receipt of the LINK_QUALITY_REQUESTmessage.

Additionally, the sensor unit 12 responds to a TX_POWER_ASSIGN messagefrom the interface unit 14. A TX_POWER_ASSIGN message instructs thesensor unit 12 to utilize a specific power level for futuretransmissions (with the exception of a LINK_QUALITY, where the transmitpower is assigned by a LINK_QUALITY_REQUEST). The sensor unit 12responds with a TX_POWER_ACKNOWLEDGE message that contains a packetindicating the assigned transmit power and the RSSI value observedduring the receipt of the TX_POWER_ASSIGN message.

The sensor unit 12 responds to a VERSION_REQUEST message from theinterface unit 14. A VERSION_REQUEST message instructs the sensor unit12 to transmit a VERSION message containing the unit's unique ID number,the version number of the firmware stored in its FLASH memory, and theRSSI value observed during the receipt of the VERSION_REQUEST message.

In some embodiments, in “LOW BATTERY” operational mode the sensor unit12 may notify the interface unit 14 that it has detected a low batterycondition. It may also attempt to reduce power consumption byeliminating or reducing the frequency of performing non-essentialfunctions. During the “LOW BATTERY” mode the bi-color LED will beextinguished at all times.

In one or more embodiments, when a low battery condition is detected,the sensor unit 12 initiates a LOW_BATTERY_WARNING message to theinterface unit 14. In some embodiments, the power level used for thistransmission is the power that was last assigned by the interface unit14, e.g., through a TX_POWER_ASSIGN message. In one implementation, theLOW_BATTERY_WARNING message instructs the interface unit 14 to transmitan acknowledgment, e.g., a LOW_BATTERY_ACKNOWLEDGE message, indicatingthat the LOW_BATTERY_WARNING was correctly received. In one embodiment,in the event that the sensor unit 12 does not receive aLOW_BATTERY_ACKNOWLEDGE message, it may increase the transmitter powerand resend the LOW_BATTERY_WARNING message. In some embodiments, thetransmitter power may be increased with each subsequent attempt tocontact the interface unit 14 until an acknowledgment, e.g., aLOW_BATTERY_ACKNOWLEDGE message, is received.

In one or more embodiments, once an acknowledgment has been received thesensor unit 12 may reduce the number of periodic updates it sends to theinterface units. Additionally, or alternatively, the sensor unit 12 mayalso reduce the number of times it wakes up to query the sensors, and/orother peripheral devices. Alternatively, once an acknowledge message hasbeen received the sensor unit 12 may not initiate further transmissions,but only acknowledges messages received from the interface unit 14.

FIG. 26 illustrates one possible implementation of the “TEST”operational mode utilized during the installation of the sensor unit 12.This process provides the installer with a quick andsimple-to-understand process for determining that the sensor unit 12 isinstalled at a location with adequate radio reception from the interfaceunit 14. In some embodiments, the “TEST” operational mode is initiatedby the interface unit 14 in response to a “Press and Hold” actuation ofthe button 820 on the interface unit 14. Still further, in someimplementations the “TEST” operational mode terminates automaticallyafter a set period of time, e.g., 15 minutes.

Further, according to some implementations, the “TEST” operational modeconsists of an exchange of radio messages between the sensor unit 12 andthe interface unit 14 to determine whether or not the sensor unit 12 ispositioned at a satisfactory location. Moreover, in someimplementations, the test operational mode allows the installer todetermine the best possible location for the sensor unit 12 relative tothe interface unit 14 before the sensor unit 12 is fixed at a location.In one or more embodiments, a location may be deemed satisfactory if thefollowing conditions are satisfied:

RSSI_(SENSOR)≥RSSI_(SENSORMIN)

RSSI_(INTERFACE)≥RSSI_(INTERFACEMIN)

P_(TXSENSOR)≤P_(TXNOMINAL)

Where RSSI_(SENSOR) is the RSSI value of the RF signal transmitted fromthe interface unit 14 as received at the sensor unit 12.RSSI_(SENSORMIN) is the minimum allowable value of RSSI_(SENSOR) toachieve communication reliability for the system. RSSI_(INTERFACE) isthe RSSI value of the RF signal transmitted from the sensor unit 12 asreceived at the interface unit 14. RSSI_(INTERFACEMIN) is the minimumallowable value of RSSI_(INTERFACE) to achieve communication reliabilityfor the system. P_(TXSENSOR) is the transmitter power employed by thesensor unit 12. P_(TXNOMINAL) is the maximum transmitter power allowedfor the sensor unit 12 to utilize for operations under normal operatingconditions. In some embodiments, the power level may typically be atleast 6.0 dB below the maximum output power achievable by thetransmitter, and may be selected to achieve the overall battery lifetimeof the sensor unit 12 is adequate.

According to some implementations, While in the “TEST” operational mode,the “TEST” operational mode flag in the FLAGS field of all messagepayloads may be SET.

Still referring to FIG. 26, in step 2610 the message transactions areinitiated by the interface unit 14 at two-second intervals, andculminate in the determination of the optimal location to install thesensor unit and/or to determine the minimum transmitter power for thesensor unit 12 to communicate with the interface unit 14 to achieve thedesired system reliability. In step 2612 the interface unit sends a testmessage to the sensor unit. Next, in step 2614 the sensor unit receivesthe signal and determines and responds with an acknowledgment message.In one or more implementations, the sensor unit then moves to step 2616where it determines the signal strength of the test message and displaysthe signal strength (e.g., as a number of blinks of the light emittingdiode). In some embodiments, as the location of the sensor unit 12 ischanged by the installer and the sensor unit 12 automatically determinesand displays the test acknowledge signal strength. According to someimplementations, the signal strength is automatically updated by thesensor unit 12 with each two-second “TEST” operational mode messageexchange. In one embodiment, the sensor unit 12 displays the signalstrength through an indicator, e.g., an LED, where, for example, theindicator blinks a number of times representing the signal strength at aparticular location. Alternatively, or additionally the indicator may bean LCD display that displays the signal strength. The installer may thenchange the location of the sensor unit 12 and by observing the signalstrength in different areas may determine a location to install thesensor unit 12. Alternatively, in some embodiments, when the location ofthe sensor unit is determined to be adequate based on the decisioncriteria, a bi-color LED may be illuminated green. If the location isdetermined to be inadequate, the bi-color LED may be illuminated red. Inone embodiment, the status of the bi-color LED is updated with eachtwo-second “TEST” operational mode message exchange. In someembodiments, this initialization process continues for a preset period,e.g., 15 minutes where the interface unit and the sensor unit exchangemessages to allow the user to find the optimal location for the sensorunit in terms of signal strength.

In some embodiments, the TEST message may be identical in form to theLINK_QUALITY_REQUEST message with the exception that the “TEST”operational mode flag in the FLAGS field of the message payload may beSET. According to some implementations, the sensor unit 12 responds witha TEST_ACKNOWLEDGE message. This message may be identical in form to theLINK_QUALITY_ACKNOWLEDGE message with the exception that the “TEST”operational mode flag in the FLAGS field of the message payload is SET.

In one implementation, in step 2620 the interface unit 14 decodes themessage to obtain the value of RSSI_(INTERFACE). In step 2622 theinterface unit determines if RSSI_(SENSOR)≥RSSI_(SENSORML). If thecondition is satisfied, in step 2624 the interface unit checks to seewhether the last message sent was a TX_POWER_INCREASE message. If thelast message received was not a TX_POWER_INCREASE message, in step 2626the interface unit 14 issues a TX_POWER_DECREASE message to the sensorunit 12. In step 2632 the sensor unit determines whether it is at theminimum TX power necessary for proper functioning, in step 2634 thesensor unit send a TX_LEAST_POWER message to the interface unit. Inresponse to this message, in step 2636, the interface unit issues aTX_LEAST_POWER_ACKNOWLEDGMENT message to the sensor unit 12.Alternatively, when in step 2632 the sensor unit is not at the minimumTX power, then in step 2638 the sensor unit 12 decreases its transmittalpower by the smallest possible amount and replies with aTX_POWER_DECREASE_ACKNOWLEDGE message.

Returning to step 2624, if the last message sent by the interface unitwas a TX_POWER_INCREASE message, in step 2644 the interface unit thenissues a TX_MINIMUM_POWER message to the sensor unit 12 notifying it ofthe transmitter power for use in future transmissions. In step 2646sensor unit decodes the message and obtains the RSSI_(SENSOR) value. Instep 2648 the sensor responds with a TX_MINIMUM_POWER_ACKNOWLEDGEmessage.

If alternatively in step 2622 RSSI_(INTERFACE)<RSSI_(INTERFACEMIN) hasbeen satisfied, in step 2628, the interface unit 14 issues aTX_POWER_INCREASE message to the sensor unit 12 notifying it to increaseits transmitter power by the smallest possible amount. In response tothe TX_POWER_INCREASE message, in step 2652 the sensor unit determinesif it is at the maximum TX power it is capable of producing. If thesensor unit is not at the maximum TX power, then in step 2658 the sensorunit 12 increases the transmitter power by the smallest allowableincrement and initiates a TX_POWER_INCREASE_ACKNOWLEDGE message to theinterface unit 14. Alternatively, if the sensor unit 12 is already setto transmit the maximum power it is capable of producing, the processcontinues to step 2654 where the sensor unit initiates a TX_MOST_POWERmessage to the interface unit 14 indicating that it may no longerincrease its transmit power. In response to this message, in step 2656the interface unit issues a TX_MOST_POWER_ACKNOWLEDGE message to thesensor unit 12.

In one embodiment, after the initializations are complete the sensorunit 12 may query all of the sensors and/or other peripheral devices andconstruct a data packet comprising atmospheric data, battery strength,signal strength, and/or other data and forward the data packet to theinterface unit 14.

An alternative implementation of “TEST” operational mode is illustratedin FIG. 22. The “TEST” operational mode is utilized during theinstallation of the sensor unit 12 to provide the installer with a quickand simple-to-understand process for determining that the sensor unit 12is installed at a location with adequate radio reception from theinterface unit 14. Further, the “TEST” operational mode is initiated bythe interface unit 14 in response to a “Press and Hold” actuation of thebutton 820 on the interface unit 14. Still further, the “TEST”operational mode terminates automatically after a period of fiveminutes.

Additionally, the “TEST” operational mode consists of an exchange ofradio messages between the sensor unit 12 and the interface unit 14 todetermine whether or not the sensor unit 12 is positioned at asatisfactory location. A location is deemed to be satisfactory if thefollowing conditions are satisfied:

RSSI_(SENSOR)≥RSSI_(SENSORMIN)

RSSI_(INTERFACE)≥RSSI_(INTERFACEMIN)

P_(TXSENSOR)≤P_(TXNOMINAL)

Where RSSI_(SENSOR) is the RSSI value of the RF signal transmitted fromthe interface unit 14 as received at the sensor unit 12.RSSI_(SENSORMIN) is the minimum allowable value of RSSI_(SENSOR) toachieve communication reliability for the system. RSSI_(INTERFACE) isthe RSSI value of the RF signal transmitted from the sensor unit 12 asreceived at the interface unit 14. RSSI_(INTERFACEMIN) is the minimumallowable value of RSSI_(INTERFACE) to achieve communication reliabilityfor the system. P_(TXSENSOR) is the transmitter power employed by thesensor unit 12. P_(TXNOMINAL) is the maximum transmitter power allowedfor the sensor unit 12 to utilize for operations under normal operatingconditions. This power level is typically at least 6.0 dB below themaximum output power achievable by the transmitter, and is selected toachieve the overall battery lifetime of the sensor unit 12 is adequate.

While in the “TEST” operational mode, the “TEST” operational mode flagin the FLAGS field of all message payloads will be SET.

Still referring to FIG. 22, in step 2210 the message transactions areinitiated by the interface unit 14 at two-second intervals, andculminate in the determination of the minimum transmitter power for thesensor unit 12 to communicate with the interface unit 14 to achieve thedesired system reliability. If the location of the sensor unit 12 isdetermined to be adequate based on the decision criteria, the bi-colorLED is illuminated green. If the location is determined to beinadequate, the bi-color LED is illuminated red. The status of thebi-color LED is updated with each two-second “TEST” operational modemessage exchange.

In step 2212 the interface unit sends a TEST message to the sensor unit12. In step 2214 the sensor unit 12 responds to the TEST message fromthe interface unit 14. The TEST message may be identical in form to theLINK_QUALITY_REQUEST message with the exception that the “TEST”operational mode flag in the FLAGS field of the message payload is SET.The sensor unit 12 responds with a TEST_ACKNOWLEDGE message. Thismessage may be identical in form to the LINK_QUALITY_ACKNOWLEDGE messagewith the exception that the “TEST” operational mode flag in the FLAGSfield of the message payload is SET.

In step 2216 the interface unit 14 decodes the message to obtain thevalue of RSSI_(INTERFACE). In step 2218 the interface unit determines ifRSSI_(SENSOR)≥RSSI_(SENSORMIN). If the condition is satisfied, in step2220 the interface unit checks to see whether the last message sent wasa TX_POWER_INCREASE message. If the last message received was not aTX_POWER_INCREASE message, in step 2222 the interface unit 14 issues aTX_POWER_DECREASE message to the sensor unit 12. In step 2224 the sensorunit determines whether it is at the minimum TX power necessary forproper functioning, in step 2228 the sensor unit send a TX_LEAST_POWERmessage to the interface unit. In response to this message, in step2230, the interface unit issues a TX_LEAST_POWER_ACKNOWLEDGMENT messageto the sensor unit 12. Following receipt of the message the sensor unitcontinues to step 2250. Alternatively, when in step 2224 the sensor unitis not at the minimum TX power, then in step 2226 the sensor unit 12decreases its transmittal power by the smallest possible amount andreplies with a TX_POWER_DECREASE_ACKNOWLEDGE message.

Returning to step 2220, if the last message sent by the interface unitwas a TX_POWER_INCREASE message, in step 2244 the interface unit thenissues a TX_MINIMUM_POWER message to the sensor unit 12 notifying it ofthe transmitter power for use in future transmissions. In step 2246sensor unit decodes the message and obtains the RSSI_(SENSOR) value. Instep 2248 the sensor responds with a TX_MINIMUM_POWER_ACKNOWLEDGEmessage. Following step 2248, in step 2250 the sensor unit determines ifRSSI_(SENSOR)≥RSSI_(SENSORMIN). When the condition is satisfied, then instep 2256 the sensor unit determines whether P_(TXSENSOR)≤P_(TXNOMINA).If this condition is satisfied, then the sensor unit continues to step2258 where the bi-color led is illuminated green, indicating that thesensor location is acceptable. Alternatively, if in step 2256 the sensorunit determines the P_(TXSENSOR)>P_(TXNOMINA) then in step 2252 thebi-color led is illuminated in red indicating that the sensor locationis unacceptable.

Similarly, if in step 2250 the sensor unit determines thatRSSI_(SENSOR)<RSSI_(SENSORMI) process continues to step 2252, where thebi-color led is illuminated in red indicating that the sensor locationis unacceptable.

Following receipt of the message, in step 2216 the interface unit 14decodes the message and obtains the value of RSSI_(INTERFACE). Theinterface unit then repeats steps 2218-2226, as described above, untilRSSI_(INTERFACE)<RSSI_(INTERFACEMIN) has been satisfied by the powerdecrease. If this condition has been satisfied, in step 2232, theinterface unit 14 issues a TX_POWER_INCREASE message to the sensor unit12 notifying it to increase its transmitter power by the smallestpossible amount. In response to the TX_POWER_INCREASE message, in step2234 the sensor unit determines if it is at the maximum TX power it iscapable of producing. If the sensor unit is not at the maximum TX power,then in step 2236 the sensor unit 12 increases the transmitter power bythe smallest allowable increment and initiates aTX_POWER_INCREASE_ACKNOWLEDGE message to the interface unit 14.Alternatively, if the sensor unit 12 is already set to transmit themaximum power it is capable of producing, the process continues to step2238 where the sensor unit initiates a TX_MOST_POWER message to theinterface unit 14 indicating that it may no longer increase its transmitpower. In response to this message, in step 2240 the interface unitissues a TX_MOST_POWER_ACKNOWLEDGE message to the sensor unit 12. Thenin step 2252 the sensor unit causes the bi-color led to be illuminatedin red indicating that the sensor location is unacceptable.

In one or more implementations the interface unit 14 draws power fromthe main irrigation controller 30. The interface unit 14 may operatefrom 22 to 30.8 VAC input voltage. Typically, the interface unit 14operates by taking 24 VAC electrical power from its associatedirrigation controller. Additionally or alternatively, the interface unitmay comprise a power source, such a battery, solar power, and/or othersuch source, where the interface unit draws some or all of its powerfrom the power source.

In some embodiments, the controller 414 of the interface unit 14 may beimplemented utilizing a low-cost 8-bit microcontroller that hassufficient computational power and speed to support all of thefunctional capabilities of the unit. In one embodiment, themicrocontroller may employ a quartz crystal for generation of aninternal clock signal. It may be desired that the same type ofcontroller and/or microcontroller be used in both the sensor unit 12 andthe interface unit 14.

According to some implementations, the controller typically employsFLASH memory for storage of executable firmware, and is capable of beingprogrammed “in-system”. For example, an in-system programming port maybe available on the printed circuit board for accomplishing theprogramming process during final assembly. The in-system programmingport may be accessible via surface pads (through the use of “pogo” pinson an ICT fixture), in one or more embodiments. A programming header mayalso be available on the printed circuit board to permit reprogrammingthe controller during firmware development. In some embodiments, thecircuit board may be designed for ease of testability such as usingautomated test fixture equipment. In this embodiment, standard solderconnections with conformal coating are used for the circuit board.

In some implementations, the controller 414 may also include on-chipEEPROM for non-volatile storage of miscellaneous data required forsupport of all functional capabilities. On-chip RAM is also typicallypresent in sufficient quantity for all functional capabilities,according to some embodiments.

In some embodiments, the interface unit employs a single-chiptransceiver 412 which provides an analog or digital Received SignalStrength Indicator (RSSI) output signal. In one embodiment, where theRSSI output is an analog signal, it may be provided to one channel ofthe controller's ADC.

The interface unit 14, according to some implementations, may also beequipped with a backlit LCD 816. The display may be capable ofdisplaying alphanumeric characters with 11-segment LCD digits. Asufficient number of LCD digits are provided to display at least thefollowing messages:

-   -   a) BATT OK    -   b) BATT LOW    -   c) BYPASS    -   d) NORMAL    -   e) INHIBIT    -   f) FREEZE    -   g) TEST    -   h) NO SIGNAL    -   i) NO SENSOR    -   j) NOISE

Additionally, or alternatively the interface unit may be capable ofdisplaying the mode and or status of the system through other means. Forexample, in one embodiment the user display 426 comprises a graphicdisplay capable of displaying the mode of operation or status of thesystem. For example, in one embodiment, the display 426 may display thestatus of the system using pictorial or graphical symbols or iconsdisplayed on the graphic display of the interface unit 14.

In some implementations, the interface unit 14 employs a “normallyclosed” relay device to permit breaking the COMMON return lineconnection between the sprinkler valve solenoids and the irrigationcontroller 30. In one or more embodiments, this relay may be actuated bya voltage that is compatible with the voltage output of one of thecontroller output pins. According to some implementations, the maximumcurrent rating of the relay contacts may be no less than 3.0 amperes.

In some embodiments, the interface unit 14 also employs a currentsensing device 420 to allow detection of the current flow in the COMMONreturn line. In one embodiment, when an irrigation cycle is commanded bythe irrigation Controller, current flows in the COMMON line. The currentsensor may detect this signal, triggering the controller 414 to initiatea SENSOR_STATUS_REQUEST to the sensor unit 12. In one embodiment, whenthe SENSOR_STATUS message returned by the sensor unit 12 indicates thatirrigation should be inhibited, the current interruption relay 416 isOPEN, interrupting irrigation.

Additionally or alternatively, the interface unit 14 may employ avoltage sensing device 422, in one or more embodiments, to allowdetection of the voltage across the current interruption relay 416 inthe COMMON return line. When irrigation is being commanded by theirrigation controller 30 while the system 10 is commanding thatirrigation be inhibited, the voltage sensor 422 may monitor the voltageacross the relay contacts to determine when the irrigation cycle hasterminated. Once the irrigation cycle has terminated the interface unit14 will CLOSE the current interruption relay.

In some embodiments, the interface unit comprises a user input 424,wherein in one or more embodiments the user input allows the user tochange the mode of operation of the interface unit and/or perform otheradjustments in the operation of the interface unit 14. For example, inone embodiment, the interface unit 14 is equipped with a three-positiontoggle switch 814 to allow the user to configure the unit for thedesired operation. The switch has a CENTER position in addition to aLEFT and a RIGHT position. Placing the switch into the CENTER positionplaces the interface unit 14 into NORMAL operational mode whereirrigation is inhibited if sufficient precipitation has been detected bythe sensor unit 12. Placing the switch into the LEFT position places theinterface unit 14 into BYPASS mode, where irrigation will not beinhibited by the system. The RIGHT switch position is a spring-loaded“return to center”, automatically releasing back to CENTER when theswitch is no longer held in position. This spring-loaded position placesthe interface unit 14 unit into TEST operational mode. The interfaceunit may also include a way too override or shut-off the device.Alternatively, and or additionally, in one embodiment, the interfaceunit 14 is equipped with a touch screen comprising buttons that allowthe user to switch the mode of operation.

In some embodiments, the interface unit 14 unit is equipped with apushbutton switch 820 to allow the user to activate an LCD backlight fora period of five seconds. When the pushbutton is depressed, the LCDbacklight is illuminated. The LCD backlight remains illuminated for aperiod of time, e.g., 5 seconds, after the pushbutton has been released.In one or more embodiments, when the toggle switch on the interface unit14 is set to the BYPASS position, the LCD display continuously displaysthe “BYPASS” message.

In many embodiments, the interface unit 14 incorporates a user-friendlymethod of adjusting the rainfall level desired by the user. For example,the interface unit 14 may be equipped with a linearly-adjustable slideswitch 812 that allows the user to select the level of precipitation atwhich irrigation will be interrupted. In one or more embodiments,precipitation amounts between ⅛″ and ¾″ are selectable in a continuousmanner.

When power is first applied to the interface unit 14, the unit powers upand enters “INITIALIZATION” operational mode. In some embodiments,during the initialization mode, the controller 414 executes theinitializations that need to be completed in order to set the unit upfor operation. During the initialization mode the interface unit mayalso attempt to pair up with one or more sensor units 12, such asillustrated in the system diagram of FIG. 34. In one implementation, theinterface unit will send a setup signal to one or more sensor units 12.Next, the interface unit may receive an acknowledgement signal from oneor more sensor units 12 in response to the setup signal. In someembodiments, the acknowledgment signal may comprise identificationand/or other information about the sensor unit. In some embodiments, theinterface unit 14 may store the data in memory 418 and/or use the datato pair up with the sensor unit 12. Once the setup is complete theinterface unit and sensor unit 12 may communicate through thecommunication link or path 15. In one embodiment, during “INITIALIZATIONMODE” the LCD backlight may be continuously illuminated.

In one embodiment, after the initializations are complete the sensorunit 12 may query all of the sensors and/or other peripheral devices andconstruct a data packet comprising atmospheric data, battery strength,signal strength, and/or other data and forward the data packet to theinterface unit 14. The interface unit 14, according to someimplementations, may receive the data from the sensor unit 12, andprocess the data and display information about the sensor unit on theuser display 426.

Additionally or alternatively, in some embodiments, at the conclusion ofthe internal initializations, the controller may retrieve from itsmemory 418, and more specifically the EEPROM, the identification numberof the sensor unit 12 with which it is associated and transmit aSENSOR_STATUS_REQUEST message. Upon receipt of a SENSOR_STATUS messagefrom the sensor unit 12, the interface unit 14 may process the message.In one embodiment, the interface unit 14 may further display theappropriate sensor unit 12 status message on the LCD display 426.

In one or embodiments, when no sensor unit is associated with theinterface unit 14, the user display 426 may display a “NO SENSOR”message and/or a similar message and or graphic display. In oneembodiment, when the “NO SENSOR” message is displayed the LCD backlightflashes on and off at a 4-second rate (two seconds on, two second off).According to one implementation, at the conclusion of the“INITIALIZATION” mode, the interface unit 14 enters “NORMAL” mode.

In some embodiments, the interface unit 14 spends the majority of itstime in the “NORMAL” operation mode. In “NORMAL” mode, the LCD backlightis OFF unless illuminated by the user by depressing the pushbutton, orby an event requiring its illumination.

In one or more embodiments, when the interface unit 14 is set to BYPASS,the current interruption relay is set to CLOSED. In one implementation,a “BYPASS” message may be continuously displayed on the LCD. In this orother implementations, The LCD backlight may be OFF.

In some embodiments, during “NORMAL” mode, the interface unit 14 willcontinually monitor the open-circuit voltage across the currentinterruption relay to detect when irrigation is being commanded from theirrigation controller 30. In this embodiment, when 24 VAC is detectedacross the current interruption relay, the interface unit 14 initiates aSENSOR_STATUS_REQUEST to its associated sensor unit 12. If theSENSOR_STATUS reply message received from the sensor unit 12 indicatesthat irrigation should be inhibited, the current interruption relay isOPENED. Once the relay has been OPENED, the interface unit 14 maymonitor the current flow in the COMMON return line to detect whenirrigation has ceased, at which time the current interruption relay isset to CLOSE. Alternatively, if the SENSOR_STATUS reply message receivedfrom the sensor unit 12 indicates that irrigation should be permitted,the current interruption relay remains in its default CLOSED state. Insome embodiments, while in normal mode, the current interruption relayis normally CLOSED, unless the SENSOR_STATUS reply message received fromthe sensor unit 12 indicates that irrigation should be inhibited. Inthese embodiments if system failure occurs at any time the relay is inits default CLOSED state.

Alternatively, in some embodiments, the interface unit will open andclose the relay based on transmission of signals initiated from thesensor unit. In one embodiment the sensor unit 12 will initiate anupdate message to the interface unit when it senses a change in one ormore of the data retrieved from sensors and/or other peripheral devices.Additionally or alternatively, the sensor unit may initiatecommunication with the interface unit 14, in some embodiments, at fixedintervals, e.g., 4 times a day, when it may query one or more sensorsand/or other devices and send an update signal to the interface unit 14.In one or more embodiments the frequency of transmission of periodicupdates based on internal and/or external criteria. For example, in oneembodiment the sensor unit 12 may decrease the number of updates it willsend the interface unit 14 during the Low Battery mode. Additionally oralternatively, the sensor unit may also reduce the number of updates ittransmits to the interface unit 14 during low temperature or hibernationmode. In some embodiments, in addition to these messages the sensor unitmay also send a message to the interface unit when it receives a requestfor data from the interface unit 14.

In one embodiment, after the SENSOR_STATUS message, or an update messageis received from the sensor unit 12, the interface unit 14 maycontinuously displays the appropriate system status message on the userdisplay 426. In one embodiment, for example:

a) when irrigation is currently enabled, the message “NORMAL” isdisplayed

b) when irrigation is currently disabled because of precipitation, themessage “INHIBIT” is displayed

c) when irrigation is currently disabled because of low temperature, themessage “FREEZE” is displayed

In one implementation, while these messages are being displayed, the LCDbacklight may be turned OFF.

Alternatively, in another exemplary embodiment, the display may be agraphical display. In this and other embodiments, the interface unit maydisplay the status and other data received from the sensor unit througha graphical representation.

In many embodiments, while in “NORMAL” operational mode the interfaceunit 14 responds to a BATTERY_OK message from the sensor unit 12. Uponreceipt of this message the interface unit 14 may send aBATTERY_OK_ACKNOWLEDGE message back to the sensor unit 12. In oneembodiment, after transmitting this message, the message “BATT OK” isdisplayed on the display for a certain period, e.g., five seconds. In analternative embodiment, the interface unit may display the batterystrength of the sensor unit 12 on the display 426.

The interface unit 14, in some embodiments, may also responds to a lowbattery warning message, e.g., a LOW_BATTERY_WARNING message, from thesensor unit 12. In one embodiment, the interface unit 14 may respond toreceipt of this message by sending a LOW_BATTERY_ACKNOWLEDGE messageback to the sensor unit 12. In one implementation, after this message istransmitted a low battery indication, e.g., a “BATT LOW” message, isdisplayed continuously on the user display 426. Additionally, in someembodiments, the LCD backlight is flashed on and off at a 4-second rate(two seconds on, two second off). In some embodiments, the otherirrigation control functions at the interface unit 14 continue tooperate normally. In one embodiment, in order to indicate this, the lowbattery indication is displayed alternately with the status indicationthat is appropriate for the current state of the system (e.g., “NORMAL”,“INHIBIT”, “FREEZE”, “BYPASS”, etc.).

In some embodiments, at fixed intervals, e.g., approximately once perday, the interface unit 14 initiates a measurement of the communicationslink quality, for example by issuing a LINK_QUALITY_REQUEST message tothe sensor unit 12. Upon receipt of the response from the sensor unit12, for example the LINK_QUALITY_ACKNOWLEDGE message, the interface unit14 determines if the value of RSSI_(INTERFACE) satisfies the condition:

RSSI_(INTERFACE)≥RSSI_(INTERFACEMIN)

In one embodiment, when RSSI_(INTERFACE)<RSSI_(INTERFACEMIN) theinterface unit 14 may send a power increase message, for example aTX_POWER_INCREASE message, to the sensor unit 12. In one embodiment thesensor unit 12 may respond to the message by increasing its transmitpower by the smallest possible amount and reply, for example with aTX_POWER_INCREASE_ACKNOWLEDGE message.

Upon receipt of this message, in one or more implementations, theinterface unit 14 may determine if the conditionRSSI_(INTERFACE)≥RSSI_(INTERFACEMIN) has been satisfied by the powerincrease. If this condition has been satisfied, the interface unit 14may issues a message, e.g., a TX_MINIMUM_POWER message, to the sensorunit 12 notifying it of the transmitter power to use for futuretransmissions. Alternatively, when this condition is not satisfied, theinterface unit 14 may continue to issue power increase requests, e.g.,TX_POWER_INCREASE messages, to the sensor unit 12 until the condition issatisfied and/or a preset period of time has lapsed. In someembodiments, when the sensor unit 12 reaches the maximum power that itmay transmit during this process, it may send a message indicating thatit has reached it maximum power level, e.g., a TX_MOST_POWER message, tothe interface unit 14. In this case, the interface unit 14 may respondwith an acknowledgment message, e.g., a TX_MOST_POWER_ACKNOWLEDGEmessage, and terminate the power adjustment process.

Alternatively, according to some embodiments, whenRSSI_(INTERFACE)≥RSSI_(INTERFACEMIN) the interface unit may 14 issues amessage to the sensor unit 12, requesting that the sensor unit 12decrease its transmit power, e.g., a TX_POWER_DECREASE message. In oneimplementation, as a result of this message the sensor unit 12 maydecrease its transmit power by the smallest possible amount and mayfurther reply with an acknowledgment message, for example aTX_POWER_DECREASE_ACKNOWLEDGE message. Upon receipt of this message, theinterface unit 14 may determine if the conditionRSSI_(INTERFACE)<RSSI_(INTERFACEMIN) has been satisfied by the powerdecrease, according to some implementations. In one embodiment, whenthis condition has been satisfied, the interface unit 14 may issue arequest to the sensor unit 12 notifying it to increase its transmitterpower by the smallest possible amount, e.g., TX_POWER_INCREASE message.The sensor unit 12 may respond to the request with an acknowledgementmessage, e.g., a TX_POWER_INCREASE_ACKNOWLEDGE message, and, in one ormore embodiments, the interface unit 14 may verify that the conditionRSSI_(INTERFACE)≥RSSI_(INTERFACEMIN) is now satisfied. The interfaceunit 14 may then issue a message to the sensor unit 12 notifying it ofthe transmitter power to use for future transmissions, e.g., aTX_MINIMUM_POWER message.

In some embodiments, so long as the conditionRSSI_(INTERFACE)<RSSI_(INTERFACEMIN) is not satisfied, the interfaceunit 14 may continue to issue requests to the sensor unit 12 notifyingit to decrease its transmitter power, e.g., a TX_POWER_DECREASEmessages, until the condition is satisfied. In one embodiment, once thesensor unit 12 reaches the minimum power that it may transmit duringthis process, it will send a message to the interface unit notifying itthat it has reached its minimum power, e.g., a TX_LEAST_POWER message.In this or other embodiments, the interface unit 14 may respond with anacknowledgment, for example a TX_LEAST_POWER_ACKNOWLEDGE message, andmay further terminate the power adjustment process.

As described with respect to FIGS. 22 and 26, the “TEST” mode may beused during the installation of the sensor unit 12 and provides a methodfor a single installer to easily determine whether or not the proposedlocation for the sensor unit 12 will result in satisfactory signalreception and communications reliability in one or more embodiments. Inone implementation, the “TEST” mode is initiated by switching the toggleswitch to “TEST” mode and holding it for a minimum of three seconds. Inthis embodiment, after this time requirement has been met, the interfaceunit 14 continuously displays an indication, e.g., the message “TEST”,on the user display 426. In one embodiment, the LCD backlight may becontinuously illuminated while in “TEST” mode. Additionally oralternatively, the test mode may be initiated through other forms ofuser input, e.g., activating a test button, selecting the test option,etc. In one embodiment, the test mode may also be initiated by theinterface unit once the interface unit is powered up and paired with oneor more sensor units.

After the test mode has been initiated, according to someimplementations, the interface unit 14 may initiate a TEST message atintervals of no more frequently than, for example, two seconds.Alternative procedures followed throughout the “TEST” mode are describedin the flowchart depicted in FIGS. 22 and 26. In some embodiments, the“TEST” mode may be terminated by the operator, for example by selectingand holding the toggle switch in the “TEST” position for a period, suchas, a period of no less than two seconds, and/or automatically after aperiod of, for example, fifteen minutes.

In many embodiments, message traffic between the interface unit 14 andsensor unit 12 typically occur in pairs, i.e., for every message that issent, there is an acknowledgement.

In one embodiment, in the event that the sender of an initial messagedoes not receive an acknowledgement corresponding to the message sentwithin a period of time (e.g., five seconds), the originator of themessage may assume that the message was lost. In one embodiment,retransmission of the message may be attempted for a period (e.g., oneminute). When the message may not be successfully transmitted andacknowledged within a period (e.g., one minute), in one or moreembodiments, the sender of the message may assume either that thecommunications channel is suffering from an unusually high level ofinterference or that a malfunction has occurred at the other end of thecommunications link.

In order to assess potential interference in the communications channel,both the interface unit 14 and the sensor unit 12 may periodicallymonitor the RSSI values obtained from the receiver chip during periodswhere no message traffic is being passed, according to some embodiments.In one embodiment, these values may be noted and stored, e.g. in ahistogram, so that a statistical archive of the distribution of noiselevels at the sensor unit 12 and interface unit 14 locations isavailable with which to assess the communications channel at any giventime. In some implementations, when no message traffic is being passed,the interface unit 14 may sample the RSSI value from its receiver chipat intervals of one minute. In one or more embodiments, the sensor unit12 may sample the RSSI value from its receiver chip at fixed intervals,e.g. one hour.

In some embodiments, after a failure to receive a timely acknowledgementto a message that has been sent, the originator of the message maysample the RSSI value from its receiver chip and may further assesswhether or not the sample obtained meets some criteria, for examplewhether the sample obtained lies within the bins of the histogramassociated with the expected noise floor. In one implementation, when itis determined that an unusually high noise level is present, an attemptat a retransmission may be made at the maximum possible transmitterpower. When this attempt fails to result in a successfulacknowledgement, in some embodiments, the device may sample the RSSIvalue from its receiver chip at fixed intervals, e.g. 15 minuteintervals, and may retransmit the message when the noise level hasreturned to its nominal value.

In one embodiment when a certain amount of time lapses without reductionin noise level the interface and/or sensor unit may cease attempts totransmit the message. For example, in one exemplary embodiment, when 24hours elapses with no reduction in the atmospheric noise level, theinterface unit 14 may ceases attempting to retransmit the message. Inone implementation of this exemplary embodiment, the interface unit maycontinuously display an indication of the presence of noise, e.g. the“NOISE” message, on the user display 426. In this embodiment, while thisindication is being displayed, the LCD backlight may be illuminatedcontinuously. In one embodiment, when the noise level has returned toits nominal level, the interface unit 14 may initiate a message, e.g. aLINK_QUALITY_REQUEST message, to re-establish the communications linkand configure the appropriate transmitter power for the sensor unit 12.In one exemplary embodiment, if 1 hour elapses with no reduction in theatmospheric noise level, the sensor unit 12, the unit may ceaseattempting to retransmit the message.

Alternatively, when sampling the RSSI value from the receiver chip, whenthe device determines that no excess atmospheric noise is present in thecommunications channel; it may presume that the device at the other endof the wireless link has failed.

In one embodiment when the interface unit 14 determines that the sensorunit 12 has failed, it may continue to attempt making contact with thesensor unit 12 at fixed intervals, e.g. five-minute intervals, for aperiod, e.g., 24 hours. In one embodiment, when no contact with thesensor unit 12 is made after a certain period of time, e.g. 24 hours,the interface unit 14 may cease further attempts at contacting thesensor unit 12 and, in one or more embodiment, may continuously displayan indication that communication has failed, e.g. the “NO SIGNAL”message, on the user display. In one embodiment, while this message isdisplayed, the LCD backlight is ON. In some embodiments, the interfaceunit may reattempt to communicate with the interface unit after a periodof time has lapsed.

Further, in some embodiment, when the sensor unit 12 determines that theinterface unit 14 has failed, it may continue to attempt making contactwith the interface unit 14 at fixed intervals, e.g. five-minuteintervals, for a certain period of time, e.g. one hour. In someembodiments, when communication has not been re-established after thisperiod, the sensor unit 12 may cease further attempts at contacting theinterface unit 14. In one embodiment, no further transmissions may beattempted until the interface unit 14 attempts to establish contact withthe sensor unit 12. Alternatively, in some embodiments, the sensor unit12 may try to reconnect to reestablish communication with the interfaceunit 14 after a certain period of time.

In some implementations of the rain sensor system 10, communicationmessages may comply with a desired Protocol. As such messages may havethe following format:

Start End Frame Message Frame Preamble Marker Length Data ChecksumMarker F5/ F5/ 1C/ 1 byte up to 255 1 byte 1D/ hex hex hex bytes hex

The preamble consists of 2 or more F5 (hex) transmissions. The purposeof the preamble is to give the receiving device an opportunity to syncup with the transmitting device.

Packet frames use the byte 1C hex as the start of frame marker and 1Dhex as the end of frame marker. When the payload contains a data byteequal to 1C or 1D, that byte is replaced by the sequence 1B, 01 or 1B,03. When the payload contains a data byte equal to 1B, that byte isreplaced by the sequence 1B, 02. Upon reception, sequences 1B, 01 arereplaced as 1C, sequences 1B, 02 are replaced as 1B, and sequences 1B,03 are replaced as 1D. This is similar to SLIP protocol used for TCP/IP.Packets start with the value 1C, and that value typically does notappear in the payload. Packets end with the value 1D, and that valuetypically does not appear in the payload. It may be desirable in someinstances that the length, message data or checksum contain thecombination of 1B followed by one of a 01, 02 or a 03.

The length element is a single byte that describes the length of themessage data element in terms of byte count. For example, a frame thathas 4 bytes in the message data element would have a length of 4. Alength of 0 would denote a blank frame. Because of the 1-bytelimitation, a message data element may not be any longer than 256 bytes.Also, if a frame has been subjected to the replacement of 1Cs with 1B,01, 1Bs with 1B, 02, or 1Ds with 1B, 03, the length describes the lengthof the intended packet before it was encoded to remove the 1Cs, 1Bs or1Ds. This provides another check of the packet's integrity.

The message data element carries the data payload for the frame. Themessage data typically has the same number of bytes as the described inthe length element.

The checksum is the logical addition (ignoring carry overflows) of thelength byte and all of the bytes in the message data element. This maybe used to ensure the integrity of the frame. Also, if a frame has beensubjected to the replacement of 1Cs with 1B, 01, 1Bs with 1B, 02, or 1Dswith 1B, 03, the checksum is performed on the intended packet before itwas encoded to remove the 1Cs, 1Bs or 1Ds. This provides another checkof the packet's integrity.

For messages that originate from the interface unit 14 the first byte ofthe message payload is desired to be 3E hex. Similarly, to comply withthe desired protocol, messages that originate from the sensor unit 12the first byte of the message payload shall be BE hex.

The following description is generally directed towards embodiments ofthe user interface (including user inputs and display outputs) of theinterface unit which may be utilized with one or more embodiments of therain sensor device/s described herein. It is understood that in someembodiments, the user interface described below may be implemented inwhole or in part in the user interface of the irrigation controller 30.Furthermore, in some embodiments, the user interface may be sharedbetween the interface unit and the controller 30.

FIG. 36 is an illustration of another embodiment of the interface unitof FIGS. 4 and 37 for use in the rain sensor system 10 of FIGS. 1 and 2.In this embodiment, the interface unit 3600 comprises a housing 3602,the user input 424 is embodied as a test button 3604, an irrigationbutton 3606, a temperature threshold button 3608 and a rain thresholdbutton 3610, while the user display 426/3706 is embodied as a displayscreen 3612. In accordance with several embodiments, the interface unit3600 is positioned near the controller 30 and couples to one or more ofthe activation lines 32. The interface unit 3600 wireless communicateswith the sensor unit 12. In operation, the interface unit 3600 receivesone or both of rainfall and temperature measurements and determineswhether irrigation to be executed by the controller 30 should be allowedor interrupted. The operation of the various buttons will be describedmore fully in the embodiment of FIG. 38.

Referring to FIG. 37, a functional diagram of the components of someembodiments of an interface unit in a rain sensor system 3700, asdepicted with regards to FIG. 2, is illustrated comprising a sensor unit12, an interface unit 3702 and the irrigation controller 30. The sensorunit 12 further comprises a sensor antenna 3712. The sensor unit 12utilizes the wireless communication link 3714 to communicate to theinterface unit 3702.

The interface unit 3702 further comprises a controller 414, a processingunit 3716, the memory 418, a display unit 3704, a display driver 3708,the user display 3706, the user input 424, the relay device 416, thetransceiver 412 and an interface antenna 3710. As mentioned above, theirrigation controller 30 further couples to activation lines 32 and mayoutput activation signals to respective ones of the plurality ofactivation lines 32, each coupled to a valve located in the region to beirrigated, or coupled to an electrical switch to activate or deactivatelighting or other devices controlled by the controller 30. As is wellknown, one or more sprinkler devices, drip lines and/or other irrigationdevices may be coupled to each valve.

In one embodiment, the sensor unit 12, interface unit 3702, andirrigation controller 30 comprise the rain sensor system 3700. Asmentioned above with respect to FIG. 2, the sensor unit 12 utilizes thesensor antenna 3712 to send data to the interface unit 3702 through thewireless communication link 3714. The interface unit 3702 receives thedata through the interface antenna 3710 and the transceiver 412. Theinterface unit 3702 further couples with the irrigation controller 30through means of the relay device 416 and the common line 34.

Within the interface unit 3702, the transceiver 412 comprises circuitryadapted to send data to and from the controller 414. User input datareceived from the user input 424 (embodied as the test button 3604, theirrigation button 3606, the temperature threshold button 3608, and therainfall threshold button 3610 in FIG. 36) is also sent to thecontroller 414. As mentioned above, the controller 414 comprisescircuitry to analyze the incoming data from the sensor unit 12 and theuser input 424 to determine whether or not irrigation from theirrigation controller should be interrupted. The controller 414 may beimplemented through a single-processor or multiprocessor systems,minicomputers, microprocessor, processor, programmable electronics andthe like, and/or combinations thereof. The controller 414 comprises theprocessor unit 3716 and the memory 418. The memory 418 may be a separatememory unit within the interface unit 3702, external memory connected tothe interface unit via an interface (not shown), may be internal memorywithin the controller 414, and/or other such configurations. Theprocessor unit 3716 comprises circuitry for executing instructions,which in some instances are defined by processor and/or computerexecutable program codes or the like, stored in memory 418 and analyzingthe given sensor unit data and user input data to determine whetherirrigation should be interrupted. Together, the processor unit 3716 andthe memory 418 work together as the controller 414 to implement thefunctionality of the interface unit 3702.

As discussed above, in one embodiment the interface unit 3702 interruptsirrigation by coupling to the common line 34 of the irrigationcontroller and further utilizing the relay device 416. When thecontroller 414 of the interface unit 3702 determines that irrigationshould be interrupted, the controller 414 sends signaling to the relaydevice 416 to open the switching device, therefore breaking the commonline 34. This effectively disables all electrical signals via theactivation lines 32 to the valves, until the switch is closed. In thisway, the irrigation controller 30 is not aware that the watering hasbeen interrupted or overridden.

The display unit 3704 comprises the user display 3706 and the displaydriver 3708. In some embodiments, the user display 3706 is anotherembodiment of user display 426. Signaling regarding various informationsuch as the threshold levels the interface unit 3702 is currently setat, notifying the user of battery strength or low battery, indicating ifthe interface unit 14 is in watering interrupt mode or not, or othersuch information is sent to the display unit 3704 from the controller414. The display driver 3708 then processes the received informationwhich is then displayed to a user on the user display 3706. The userdisplay 3706 may be one or more of a display screen, liquid crystaldisplay (LCD), touch screen display, lights, LEDs, and/or other relevantdisplays.

While the components within the interface unit 3702, such as thecontroller 414, the transceiver 412, the interface antenna 3710, therelay device 416, and the display unit 3704 are depicted as separateentities, it should be appreciated that these components may be combinedtogether as one component, or any combination thereof.

Referring next to FIG. 38, an embodiment is shown of a user interface3800 of the interface unit of FIG. 36 illustrating the user interface inthe form of user inputs and display outputs. The user interfacecomprises a test button 3802, an irrigation button 3804, a temperaturethreshold button 3806, a rainfall threshold button 3808, a displayscreen 3810, and various icons and/or graphical, pictorial or otherrepresentations or visual indications which may be displayed at anygiven time on the display screen.

In one embodiment, the test button 3802 is utilized to initiate initialinstallation or to initiate the test mode for the interface unit. Theirrigation button 3804 is utilized to alter the irrigation mode of theinterface unit. The irrigation mode of the interface unit determinesunder what sensed weather conditions, such as rainfall and temperature,irrigation executed by an irrigation controller is to be interrupted. Inone embodiment, the temperature threshold button 3806 and the rainfallthreshold button 3808 are utilized to set the temperature thresholdpoint and the rainfall threshold point respectively. In someembodiments, by pressing the rainfall threshold button 3610, the userswitches the rainfall threshold point between multiple discrete levelsof rain threshold, e.g. a low threshold, a mid threshold and a highthreshold. In some embodiments, by pressing the temperature thresholdbutton 3608, the user switches the temperature threshold point betweenmultiple discrete levels of temperature. In some embodiment, therainfall threshold point sets the minimum amount of rainfall sensedbefore irrigation is interrupted. On the same note, in some embodiments,the temperature threshold point sets the maximum sensed temperaturebefore irrigation is interrupted. The various ways which these buttonsalter what is displayed on the display screen 3810 will be discussed infurther detail below.

The display screen 3810 is configured to display a plurality of iconswhich convey information about the rain sensor system, such asindicating which threshold levels the interface unit 14 is currently setat, notifying the user of battery strength or low battery, indicating ifthe interface unit 14 is in watering interrupt mode or not, and othersuch information. Thus, in a generic sense, the various icons may bereferred to as visual indicators. In one embodiment, the display screen3810 may be divided into three separate regions: a system communicationand status display area 3812, an irrigation mode display area 3814, anda sensor data and thresholds display area 3816. The systemcommunications and status display area 3812 displays informationregarding the connectivity between devices in the rain sensor system orthe current operational status of the various sensor units configured tocommunicate with the interface unit. The status display area 3812displays icons such as a battery remaining indicator 3818, a signalstrength indicator 3820, a test mode indicator 3822, and a sensorcommunication indicator 3824.

The battery remaining indicator 3818 is disposed to the upper leftcorner of the system communications and status display area 3812. Thebattery remaining indicator 3818 displays the strength of the battery ofthe sensor unit 12. The battery remaining indicator 3818 is filled witha varying number of dark bars which indicate battery strength. When thebattery remaining indicator 3818 is completely filled with dark bars,then the battery of the sensor unit is at full strength. As the batterystrength of the sensor unit 12 depletes, the battery remaining indicator3818 will display fewer bars. The number of bars displayed within thebattery remaining indicator 3818 roughly corresponds to the amount ofbattery strength left in the sensor unit. For example, in one embodimentthe battery remaining indicator 3818 is filled with four dark bars whenthe battery strength of the sensor unit is at its max. When the batterystrength of the sensor unit is roughly at half strength, then thebattery remaining indicator 3818 would be filled with two dark bars.Once the battery remaining indicator 3818 is filled with either one orno bars, this should signal to a user to change the battery of the givensensor unit. As described herein, the sensor unit 12 is configured tosend information about its battery strength to the interface unit.

The signal strength indicator 3820 is disposed to the upper middle ofthe system communication and status display area 3812. The signalstrength indicator 3820 illustrates the strength of signaling via thecommunication link between the connected interface unit and sensor unit.In one embodiment, the signal strength indicator 3820 illustrates thestrength of the radio signal (e.g., in terms of signal to noise) betweenthe interface unit (14, 3600, 3702) and the given sensor unit 12. Thesignal strength indicator 3820 comprises a plurality of bars ofincreasing heights. The number of bars represents the strength of thesignals received from the sensor unit at the interface unit.

The test mode indicator 3822 is disposed on the upper right corner ofthe system communication and status display area 3812. The test modeindicator 3822 indicates whether there is a connection between theinterface unit and the sensor unit. In addition, the test mode indicator3822 indicates whether the interface unit is in test or install mode.Further details regarding test and install mode will be discussed withrespect to FIGS. 40 and 41.

The sensor communication indicator 3824 is roughly disposed in thecenter of the system communication and status display area 3812. Thesensor communication indicator 3824 illustrates the current statusbetween the link between the interface unit (represented as icon 3823)and the connected sensor unit (represented as icon 3825). As illustratedin FIG. 38, the sensor communication indicator 3824 includes a sensorunit indicator 3826 to convey to the user which sensor unit theinterface unit is currently communicating with. In FIG. 38, the sensorunit indicator 3826 is indicating that the user interface iscommunicating with the sensor unit configured as “1.” Therefore theinformation illustrated in the system communications and status displayarea 3812, such as the battery remaining indicator 3818, signal strengthindicator 3820, and the sensor communication indicator 3824, correspondto the sensor unit configured as sensor unit “1.” In one embodiment, thesensor unit indicator 3826 may toggle between 1 and 5, indicating thatup to five sensor units may be connected to a single interface unit.

The sensor communication indicator 3824 illustrates the current statusof the link (or communication) between the interface unit and the givensensor unit indicated by the sensor unit indicator 3826. The sensorcommunication indicator 3824 comprises of two icons 3823 and 3825exemplifying the interface unit and the sensor unit, respectively. Whena straight line exists between the icons of the interface unit and thesensor unit, then the link is “good” or communication between theinterface unit and the indicated sensor unit is currently active. Whenthe link is a broken line, as depicted in FIG. 40, then link is brokenand communication between the interface unit and the indicated sensor isnot active.

The irrigation mode display area 3814 displays information regarding thecurrent irrigation mode which the interface unit is set. In FIG. 38, theirrigation mode display area 3814 comprises icons depicting anirrigation valve 3828 (e.g., a rotor), sprayed water 3830, a sun 3832, arain cloud 3834, and a snowflake 3836. The various combinations of theseicons indicate to a user which irrigation mode the interface unit is setin. For example, when the irrigation mode display area 3814 comprisesthe irrigation valve 3828, the sprayed water 3830, and the sun 3832,then the irrigation mode is set to normal irrigation. The normalirrigation mode allows irrigation executed by the irrigation controller30 to continue as scheduled when sensed rainfall is below the rainfallthreshold and the sensed temperature is above a given temperaturethreshold. The various irrigation modes will be discussed in furtherdetail with regards to FIGS. 45a -d.

The sensor data and thresholds display area 3816 displays informationreceived from the connected sensor unit regarding the amount of rainfallsensed and the sensed temperature. The sensor data and thresholdsdisplay area 3816 comprises icons such as a rainfall indicator 3838, arainfall threshold 3840, a rain trip indicator 3842, a temperatureindicator 3844, a temperature threshold 3846, a temperature tripindicator 3848 and low temperature indicator 3850 (shown in FIG. 46d ).

The rainfall indicator 3838 illustrates the amount of moisture currentlypresent at the sensor unit 12. The rainfall indicator 3838 fills withdark horizontal bars as rainfall is collected at the sensor unit. Therainfall threshold 3840 is exemplified as an arrow which may toggle upand down the height of the rainfall indicator 3838. As discussed above,a user utilizes the rainfall threshold button 3808 to set the rainfallthreshold point, indicating what level of rainfall would need to besensed to prompt the interface unit to interrupt irrigation. Therainfall threshold 3840 displays to the user the selected rainfallthreshold point with respect to the rainfall indicator 3838. In oneembodiment, as the user presses the rainfall button 3808, the rainfallthreshold 3840 is raised within the rainfall indicator 3838. Once therainfall threshold 3840 reaches the top of the rainfall indicator 3838,further depression of the rainfall button 3808 will cause the rainfallthreshold 3840 to wrap to the bottom of the rainfall indicator 3838 andrepeat as above. When the rainfall threshold 3840 is closer to the topof the rainfall indicator 3838, the user has selected a high rainfallthreshold point allowing the irrigation controller to continueirrigation even though a high level of moisture may be detected. Therain trip indicator 3842 is exemplified as a rain cloud which appearswhen the interface unit determines that the moisture sensed by a givensensor unit has risen above the rainfall threshold (as is illustrated).

The temperature indicator 3844 illustrates the temperature currentlypresent in the rain sensor system. The temperature indicator 3844 isexemplified as a thermometer; the amount of dark fill in the thermometerillustrates the sensed temperature. Disposed to the side of thetemperature indicator 3844 is the temperature threshold 3846 which isexemplified as an arrow which toggles up and down the height of thetemperature indicator 3844. The temperature threshold 3846 illustratesthe selected sensitivity for interrupted irrigation during lowtemperature. As discussed above, a user utilizes the temperaturethreshold button 3806 to set the temperature threshold point, in someembodiments, indicating at the maximum temperature would need to besensed to prompt the interface unit to interrupt irrigation. Thetemperature threshold 3846 displays to the user the selected temperaturethreshold point with respect to the temperature indicator 3844. Similarto the rainfall threshold, in one embodiment, the user may press thetemperature threshold button 3806 to alter the temperature threshold3846. Once the temperature threshold 3846 reaches the top of thetemperature indicator 3844, further depression of the temperaturethreshold button 3806 causes the temperature threshold 3846 to wrap backto the bottom of the temperature indicator 3844 and repeat as above. Thetemperature trip indicator 3848 is exemplified as a snowflake whichappears on the display screen 3810 when the interface unit determinesfrom measurements sent from the sensor unit that the temperature hasdropped below the temperature threshold 3846. In addition, a lowtemperature indicator 3850, exemplified as a snowflake at the bottom ofthe temperature indicator 3844 (further depicted in FIG. 46d ), appearsonce the interface unit determines that temperature detected by thesensor unit is approximately at the freezing point.

Referring to FIG. 39, one embodiment of the user interface 3800 of theinterface unit during initial power up of the interface unit isillustrated. When the interface unit is first powered up, the irrigationmode display area 3814 is set to normal mode, while no rainfall ortemperature has yet to be sensed in the sensor data and thresholdsdisplay area 3816. Default rainfall and temperature thresholds areillustrated. At the initial power up of the interface unit, only thesensor communication indicator 3824 is displayed in the systemcommunication and status display area 3812 of the display screen 3810.The straight or broken line between the icons 3823 and 3825 exemplifyingthe interface unit and the sensor unit, respectively, in the sensorcommunication indicator 3824 has disappeared. In addition, the icons3823 and 3825 of the interface unit and the sensor unit flash until aninterface unit and a sensor unit are communicationally paired together.

Referring next to FIG. 40, one embodiment of the user interface 3800 ofthe interface unit when the system is pairing with the rainfall sensordevice is illustrated. As in the initial power up, the irrigation modedisplay area 3814 is set to normal mode, while no rainfall ortemperature has yet to be sensed in the sensor data and thresholdsdisplay area 3816.

To begin install mode and pairing the interface unit with a given sensorunit, the user presses the test button 3802 for a given amount of time.In some embodiments, the given amount of time is roughly 5 seconds.Next, the user inserts a power unit into the sensor unit. In someembodiments, a battery cassette is utilized as a power unit to providepower to the sensor unit. While the sensor unit and the interface unitis pairing, the system communication and status display area 3812displays the test mode indicator 3822, indicating to the user thatcommunication between the interface unit and the sensor unit iscommencing and the interface unit is in install mode. The systemcommunication and status display area 3812 also displays the systemcommunication indicator 3824 and sensor unit indicator 3826. For thisexample, the sensor unit indicator 3826 is set to “1,” as this is thefirst time the interface unit is paired to a sensor unit. It should beappreciated that the sensor unit indicator 3826 may be set to adifferent number, corresponding to a different sensor unit. Duringinstall mode, or pairing of the interface unit and the sensor unit, thesystem communication indicator 3824 displays a broken line between theicons 3823 and 3825 representing the interface unit and the sensor unit,since the communication link between the two devices has yet to beestablished. Once install mode is complete and the interface unit haspaired with the sensor unit, the display screen 3810 will display thebattery remaining indicator 3818, the signal strength indicator 3820,the test mode indicator 3822, the signal communication indicator 3824with a straight solid line between then icons 3823 and 3825 representingthe interface and sensor unit, and the sensor unit indicator 3826. Thisdisplay indicates to the user that pairing was successful and thedisplay eventually disappears in a specified amount of time. FIG. 41provides an example of the system communication and status display area3812 that is displayed to a user to indicate that the pairing of theinterface unit and sensor unit was successfully completed.

In one embodiment, as described herein, the sensor unit is equipped witha lighting mechanism to communicate to the user the signal strengthbetween the sensor unit and the interface unit to help determine theoptimal location for the sensor unit. For the embodiment where thesignal strength may be exemplified between 1 and 4 bars, the sensor unitmay utilize the lighting mechanism to represent the number of bars inthe signal strength indicator 3820. In one embodiment, the lightingmechanism is an LED which blinks the number of signal strength bars. Forexample, if there are four bars of signal strength indicated by thesignal strength indicator 3820, the LED on the sensor unit will blinkfour consecutive times before pausing and then repeats the blinkinguntil an alteration in the signal strength indicator 3820 has beendetected or a specified time frame for determining the optimal locationof the sensor unit has elapsed. In one embodiment, the specified timeframe is roughly five minutes, meaning the user is allotted a fiveminute window to select the sensor unit location before the lightmechanism ceases representing the signal strength. This feature providesmany advantages, namely, a user would be able to install the sensor unitand the interface unit without the need of assistance from other userssince the sensor unit itself provides feedback regarding the signalstrength. FIG. 43 provides a chart 4300 illustrating the interactionbetween the signal strength indicated by the signal strength indicator3820 at the interface unit and the indicator light (e.g., LED) of thesensor unit 12 in accordance with one embodiment.

When a user wishes to test the rain sensor system or the connectionbetween the interface unit and the sensor unit, the user depresses testbutton 3802. If no sensor units are paired with the system, theinterface unit sends out a wireless pairing signal to find the closestsensor unit then begins the install mode outlined above. However, whensensor units are paired to the interface unit, pressing the test button3802 causes the interface unit to display the last known systeminformation of the given interface unit in the system communication andstatus display area 3812. Pressing the test button allows the user tocycle through each paired sensor unit, the sensor unit indicator 3826indicates to the user which sensor unit the interface unit is currentlycommunicating with, and displays the last known communication and systeminformation for the sensor indicated by the sensor unit indicator 3826.Pressing the test button 3802 cycles through the paired sensor unitsuntil reaching the first unpaired sensor position (if a sensor positionis available). If a sensor unit and a sensor position are available (thesensor position is indicted by the sensor unit indicator 3826), apairing signal is sent from the interface unit to the sensor unit andinstall mode as outlined above commences.

FIG. 42 illustrates an example of the system communication and statusdisplay area 3812 during test mode. The test button 3802 has beendepressed a certain number of times such that the interface unit iscommunicating with the sensor unit in the second sensor positionindicated by the sensor unit indicator 3826 currently at “2.” From theexample of FIG. 42, the system communication and status display area3812 illustrates that the sensor unit is at full battery power, howeverthe signal strength is not at full strength. The system communicationand status display area 3812 is visible on the display screen for aspecified amount of time. In one embodiment, the system communicationand status display area 3812 is visible for roughly ten seconds.

Referring next to FIG. 44, one embodiment of the user interface of theinterface unit once the interface unit has been paired to the rainfallsensor device is illustrated. As mentioned above, in one embodiment, theicons found within the system communication and status display area 3812has disappeared from the display screen 3810. The display screen 3810displays the icons within the irrigation mode display area 3814 and thesensor data and thresholds display area 3816. For the display screen3810 of FIG. 44, the interface unit is in normal mode, no precipitationhas been sensed, and temperature is above the temperature threshold3846.

Referring to FIGS. 45a-d , one embodiment of the irrigation mode displayarea of the interface unit depicting various irrigation modes isillustrated. The various irrigation modes include a normal irrigationmode 4502, a bypass rain mode 4504, a bypass rain/freeze mode 4506 and ahalt irrigation mode 4508. When displayed, these irrigation modesrepresent the current irrigation mode of the interface unit. Inaddition, the user may set the irrigation mode by pressing theirrigation button 3804.

FIG. 45a illustrates the normal irrigation mode 4502 for the interfaceunit. When the interface unit is in the normal irrigation mode 4502, theinterface unit displays the icons of the irrigation valve 3828, thesprayed water 3830, and the sun 3832 in the irrigation mode display area3814. During the normal irrigation mode 4502, the interface unit doesnot interrupt the irrigation schedule of the irrigation controller 30,i.e., it allows the controller 30 to irrigate as it is programmed.However, the normal irrigation mode 4502 is shut off when the interfaceunit determines that the rainfall sensed is above the rainfall threshold3840, or determines when the sensed temperature drops below thetemperature threshold 3846. In addition, the normal irrigation mode 4502may be viewed as the default mode, since the system will revert back tothe normal irrigation mode 4502 after a given amount of time from any ofthe other three irrigation modes. In one embodiment, the interface unitwill revert back to the normal irrigation mode 4502 after three daystime.

FIG. 45b illustrates the bypass rain mode 4504 depicted on theirrigation mode display area 3814. When the interface unit is in thebypass rain mode 4504, the interface unit displays the icons of theirrigation valve 3828, the sprayed water 3830, the sun 3832, and therain cloud 3834 in the irrigation mode display area 3814. During thebypass rain mode 4504, the interface unit allows the irrigationcontroller to irrigate during fair weather or when it is raining. Theinterface unit determines that it is raining when the rainfall sensed(as illustrated in the rainfall indicator 3838) rises above the rainfallthreshold 3840, or the rainfall sensed by the sensor unit is increasing.However, during the bypass rain mode 4504, the interface unit interruptsirrigation when a low temperature condition (e.g., a “freeze” condition)is sensed, the low temperature condition occurring when the sensedtemperature falls below the temperature threshold 3846. The interfaceunit returns to the normal irrigation mode 4502 when either the usermanually returns the interface unit to normal irrigation mode 4502 bypressing the irrigation button 3804, after the occurrence of one rainevent (after the rain trip indicator 3842 is displayed once), orautomatically after a given time span. In one embodiment, the given timespan is roughly three days or seventy-two hours.

FIG. 45c illustrates the bypass rain/freeze mode 4506 depicted on theirrigation mode display area 3814. When the interface unit is in thebypass rain/freeze mode 4506, the interface unit displays the icons ofthe irrigation valve 3828, the sprayed water 3830, the sun 3832, therain cloud 3834, and the snowflake 3836 in the irrigation mode displayarea 3814. During the bypass rain/freeze mode 4506, the interface unitallows the irrigation controller to irrigate during fair weather, rain,or when a low temperature condition (e.g., a freeze condition) isdetermined. The interface unit returns to the normal irrigation mode4502 when either the user manually returns the interface unit to normalirrigation mode 4502 by pressing the irrigation button 3804, after theoccurrence of one rain event or a freeze condition, or automaticallyafter a given time span. In one embodiment, the given time span isroughly three days or seventy-two hours.

FIG. 45d illustrates the halt irrigation mode 4508 (also referred to asan interrupt irrigation mode) depicted on the irrigation mode displayarea 3814. When the interface unit is in the halt irrigation mode 4508,the interface unit displays the icons of an irrigation valve 3828 andthe sun 3832. In the halt irrigation mode 4508, the icon for theirrigation valve 3828 differs from the normal irrigation valve 3828 inthat an “X” is added to the icon for the irrigation valve 3828 toindicate that irrigation from the irrigation controller should beinterrupted, hence the absence of the sprayed water 3830. During thehalt irrigation mode 4508, the interface unit interrupts irrigation fromthe irrigation controller 30. When the halt irrigation mode 4508 istriggered by a user, irrigation is interrupted regardless of the sensedweather conditions. The user may manually place the interface unit intothe halt irrigation mode 4508 by selecting the mode through theirrigation button 3804. In addition, the interface unit may enter intothe halt irrigation mode 4508 from either the normal irrigation mode4502 or the bypass rain mode 4504. The interface unit enters into thehalt irrigation mode 4508 from normal irrigation mode 4502 when theinterface unit determines that a rain or low temperature conditionexists, for example, based on temperature and/or rainfall measurementsreceived from the sensor unit according to the techniques describedherein. The interface unit enters into the halt irrigation mode 4508from the bypass rain mode 4504 when it is determined that a lowtemperature condition exists. The interface unit returns to the normalirrigation mode 4502 when either the user manually returns the interfaceunit to the normal irrigation mode 4502 by pressing the irrigationbutton 3804 or automatically after a given time span. In one embodiment,the given time span is roughly three days or seventy-two hours.

FIGS. 46a-d illustrate the relationship between the sensed rainfall andtemperature depicted in the rainfall indicator 3838 and temperatureindicator 3844 to the rain trip indicator 3842, temperature tripindicator 3848, and the temperature indicator 3850 (see FIG. 46d ).

FIG. 46a illustrates an embodiment of the sensor data and thresholdsdisplay area 3816 when the sensed rainfall is below the rainfallthreshold 3840 and the sensed temperature is above the temperaturethreshold 3846. From FIG. 46a , the dark horizontal bars vertically fillthe rainfall indicator, however the bars fall below the rainfallthreshold 3840. On a similar note, the temperature indicator 3844depicts the sensed temperature to be above the temperature threshold3846. Since neither the sensed rainfall has fallen above the rainfallthreshold 3840 nor the sensed temperature has fallen below thetemperature threshold 3846 (as determined by the interface unit based onmeasurements from the sensor unit), the area of the display screen 3810which normally displays the rain trip indicator 3842 or the temperaturetrip indicator 3848 is empty.

FIG. 46b illustrates an embodiment of the sensor data and thresholdsdisplay area 3816 when the sensed rainfall is above the rainfallthreshold 3840 and the sensed temperature is above the temperaturethreshold 3846. The dark horizontal bars within the rainfall indicator3838 exceed the rainfall threshold 3640. In response to the sensedrainfall exceeding the rainfall threshold 3840, the rain trip indicator3842 is displayed on the display screen 3810 in the sensor data andthreshold display area 3816. By displaying the rain trip indicator 3842,the interface unit conveys that a rain event is occurring. In addition,the interface unit may determine a rain event is occurring if the darkhorizontal bars within the rainfall indicator 3838 are graduallyincreasing upward, trigger the interface unit to display the rain tripindicator 3842. The temperature indicator 3844 depicts the sensedtemperature to be above the temperature threshold 3846, therefore thearea of the display screen 3810 which normally displays the temperaturetrip indicator 3848 is empty.

FIG. 46c illustrates an embodiment of the sensor data and thresholdsdisplay area 3816 when the sensed rainfall is above the rainfallthreshold 3840 and the sensed temperature is below the temperaturethreshold 3846. The dark horizontal bars within the rainfall indicator3838 exceed the rainfall threshold 3640. In response to the sensedrainfall exceeding the rainfall threshold 3840, the rain trip indicator3842 is displayed on the display screen 3810 in the sensor data andthreshold display area 3816. By displaying the rain trip indicator 3842,the interface unit conveys that a rain event is occurring. Thetemperature indicator 3844 depicts the sensed temperature to be belowthe temperature threshold 3846. In response, the interface unit displaysthe temperature trip indicator 3848 to indicate a low temperaturecondition has occurred.

FIG. 46d illustrates an embodiment of the sensor data and thresholdsdisplay area 3816 when the sensed rainfall is below the rainfallthreshold 3840 and the sensed temperature is significantly below thetemperature threshold 3846. No dark horizontal bars fill the rainfallindicator 3838, indicating the sensor unit has not sensed any rainfallor moisture. For this example, since there is no sensed rainfall, thesensed rainfall falls below the rainfall threshold 3840 and the area ofthe display screen 3810 which normally displays the rain trip indicator3842 is empty. The temperature indicator 3844 depicts the sensedtemperature to have dropped below the freezing point, or 32 degreesFahrenheit (i.e., 0 degrees Celsius). Since the sensed temperature hasdropped so low, the interface unit displays the low temperatureindicator 3850, which is embodied as a snowflake embedded within thetemperature indicator 3844. In addition, the temperature trip indicator3848 is displayed to indicate the determination of a freeze condition.

FIGS. 47-49 illustrate the relationship between the sensor data, such assensed rainfall and temperature, and the subsequent effects toirrigation mode and what is displayed in the irrigation mode displayarea 3814 of the display screen 3810 when the interface unit isinitially in the normal irrigation mode 4502.

FIG. 47 illustrates an embodiment of the display screen of the interfaceunit when the sensed rainfall is above the rainfall threshold 3840 andthe sensed temperature is above the temperature threshold 3846. The darkhorizontal bars within the rainfall indicator 3838 exceed the rainfallthreshold 3840. In response to the sensed rainfall exceeding therainfall threshold 3840, the rain trip indicator 3842 is displayed onthe display screen 3810 in the sensor data and threshold display area3816. By displaying the rain trip indicator 3842, the interface unitconveys that a rain event is occurring. The temperature indicator 3844depicts the sensed temperature to be above the temperature threshold3846, therefore the area of the display screen 3810 which normallydisplays the temperature trip indicator 3848 is empty.

Since the interface unit has determined a rain event is occurring, asmentioned above with regards to the normal irrigation mode 4502, theinterface unit interrupts the irrigation of the irrigation controller.The interface unit then displays the halt irrigation mode 4508 toindicate to a user that the interface unit is inhibiting/interruptingirrigation. The interface unit returns to normal irrigation mode 4502when the rain fall sensed by the rainfall indicator 3838 falls below therainfall threshold 3840.

FIG. 48 illustrates an embodiment of the display screen of the interfaceunit when the sensed rainfall is below the rainfall threshold 3840 andthe sensed temperature is below the temperature threshold 3846. No darkhorizontal bars fill the rainfall indicator 3838, indicating the sensorunit has not sensed any rainfall or moisture. For this example, sincethere is no sensed rainfall, the sensed rainfall falls below therainfall threshold 3840 and the area of the display screen 3810 whichnormally displays the rain trip indicator 3842 is empty. The temperatureindicator 3844 depicts the sensed temperature to be below thetemperature threshold 3846. In response, the interface unit displays thetemperature trip indicator 3848 to indicate a freeze condition hasoccurred. It is noted that the freeze condition as used herein may bebroadly referred to as a low temperature condition. That is, the lowtemperature condition may not strictly correspond to a freeze, butsimply to a defined low temperature.

Since the interface unit has determined a freeze condition is occurring,as mentioned above with regards to the normal irrigation mode 4502, theinterface unit interrupts the irrigation of the irrigation controller.The interface unit then displays the halt irrigation mode 4508 toindicate to a user that the interface unit is inhibiting/interruptingirrigation. The interface unit returns to normal irrigation mode 4502when the temperature sensed by the temperature indicator 3844 risesabove the temperature threshold 3846.

FIG. 49 illustrates an embodiment of the display screen of the interfaceunit when the sensed rainfall is below the rainfall threshold 3840 andthe sensed temperature is significantly below the temperature threshold3846. No dark horizontal bars fill the rainfall indicator 3838,indicating the sensor unit has not sensed any rainfall or moisture. Forthis example, since there is no sensed rainfall, the sensed rainfallfalls below the rainfall threshold 3840 and the area of the displayscreen 3810 which normally displays the rain trip indicator 3842 isempty. The temperature indicator 3844 depicts the sensed temperature tohave dropped below the freezing point, or 32 degrees Fahrenheit. Sincethe sensed temperature has dropped so low, the interface unit displaysthe low temperature indicator 3850, which is embodied as a snowflakeembedded within the temperature indicator 3844. In addition, thetemperature trip indicator 3848 is displayed to indicate thedetermination of a freeze condition.

Since the interface unit has determined a freeze condition is occurring,as mentioned above with regards to the normal irrigation mode 4502, theinterface unit interrupts the irrigation of the irrigation controller.The interface unit then displays the halt irrigation mode 4508 toindicate to a user that the interface unit is inhibiting/interruptingirrigation. The interface unit returns to normal irrigation mode 4502when the temperature sensed by the temperature indicator 3844 risesabove the temperature threshold 3846.

It should be understood that when the interface unit is initially innormal irrigation mode 4502 and both a rain event and a freeze conditionis occurring at the same time, the interface unit interrupts irrigationand displays the halt irrigation mode 4508 in the irrigation modedisplay area 3814. In essence, the display screen 3810 would display thehalt irrigation mode 4508 in the irrigation mode display area asdepicted by FIG. 45d along with the sensor data and threshold displayarea 3816 of FIG. 46c . In addition, if the temperature drops to thefreezing point (32 degrees Fahrenheit) or below, the low temperatureindicator 3850 would also be present on the display screen 3810.

FIGS. 50-53 illustrate the relationship between the sensor data, such assensed rainfall and temperature, and the subsequent effects toirrigation mode and what is displayed in the irrigation mode displayarea 3814 and the sensor data and threshold display area 3816 of thedisplay screen 3810 when the interface unit is in either the bypass rainmode 4504, the bypass rain/freeze mode 4506, or the halt irrigation mode4508.

FIG. 50 illustrates an embodiment of the display screen of the interfaceunit when the interface unit is in the bypass rain mode 4504 and thesensed rainfall is above the rainfall threshold 3840 and the sensedtemperature is above the temperature threshold 3846. The dark horizontalbars within the rainfall indicator 3838 exceed the rainfall threshold3640. In response to the sensed rainfall exceeding the rainfallthreshold 3840, the rain trip indicator 3842 is displayed on the displayscreen 3810 in the sensor data and threshold display area 3816. Bydisplaying the rain trip indicator 3842, the interface unit conveys thata rain event is occurring. In addition, the interface unit may determinea rain event is occurring if the dark horizontal bars within therainfall indicator 3838 are gradually increasing upward, trigger theinterface unit to display the rain trip indicator 3842. The temperatureindicator 3844 depicts the sensed temperature to be above thetemperature threshold 3846, therefore the area of the display screen3810 which normally displays the temperature trip indicator 3848 isempty.

Since the interface unit is in the bypass rain mode 4504, even thoughthe interface unit has determined a rain event is currently occurring,the interface unit does not interrupt the irrigation schedule of theirrigation controller 30. Once the interface unit has determined therain event has passed (when the sensed rainfall in the rainfallindicator 3838 has fallen below the rainfall threshold 3840), theinterface unit returns to normal irrigation mode 4502. In addition, theinterface unit may also return to normal irrigation mode 4502 fromeither the user manually returning the interface unit to normalirrigation mode 4502 by pressing the irrigation button 3804 orautomatically after a given time span, typically three days orseventy-two hours.

If the interface unit determined a freeze condition existed while in thebypass rain mode 4504, the interface unit would proceed to the haltirrigation mode 4508 and interrupt the irrigation controller 30. Theinterface unit would then display on the display screen 3810 theirrigation mode display area 3814 and sensor data and threshold displayarea 3816 of FIG. 48. Alternatively, the interface unit would display onthe display screen 3810 the irrigation mode display area 3814 and sensordata and threshold display area 3816 of FIG. 49 if a freeze conditionand conditions to trigger the display of the low temperature indication3850 existed.

FIG. 51 illustrates an embodiment of the display screen of the interfaceunit when the interface unit is in the bypass rain/freeze mode 4506 whenthe sensed rainfall is below the rainfall threshold 3840 and the sensedtemperature is below the temperature threshold 3846. No dark horizontalbars fill the rainfall indicator 3838, indicating the sensor unit hasnot sensed any rainfall or moisture. For this example, since there is nosensed rainfall, the sensed rainfall falls below the rainfall threshold3840 and the area of the display screen 3810 which normally displays therain trip indicator 3842 is empty. The temperature indicator 3844depicts the sensed temperature to be below the temperature threshold3846. In response, the interface unit displays the temperature tripindicator 3848 to indicate a freeze condition has occurred. It should beunderstood that a rain event may not be detected, and therefore the raintrip indicator 3842 is not displayed, if the sensed rainfall is lessthan the rainfall threshold 3840.

Since the interface unit is in the bypass rain/freeze mode 4506, eventhough the interface unit has determined a freeze condition is currentlyoccurring, the interface unit does not interrupt the irrigation scheduleof the irrigation controller 30. Once the interface unit has determinedthe freeze condition has passed (when the sensed temperature has risenabove the temperature threshold 3846), the interface unit returns tonormal irrigation mode 4502. In addition, the interface unit may alsoreturn to the normal irrigation mode 4502 from either the user manuallyreturns the interface unit to normal irrigation mode 4502 by pressingthe irrigation button 3804 or automatically after a given time span,typically three days or seventy-two hours.

If instead a rain event was sensed instead of a freeze condition whenthe interface unit is in bypass rain/freeze mode 4506, the interfaceunit does not interrupt the irrigation schedule of the irrigationcontroller 30 even when a rain event is determined. In this event, theinterface unit would display on the display screen 3810 the irrigationmode display area of FIG. 45c in conjunction with the sensor data andthreshold display area displayed in FIG. 46b . Once the interface unithas determined the rain event has passed (when the sensed rainfall inthe rainfall indicator 3838 has fallen below the rainfall threshold3840), the interface unit returns to normal irrigation mode 4502.

FIG. 52 illustrates an embodiment of the display screen of the interfaceunit when the interface unit is in bypass rain/freeze mode 4506 when thesensed rainfall is above the rainfall threshold 3840 and the sensedtemperature is below the temperature threshold 3846. The dark horizontalbars within the rainfall indicator 3838 exceed the rainfall threshold3640. In response to the sensed rainfall exceeding the rainfallthreshold 3840, the rain trip indicator 3842 is displayed on the displayscreen 3810 in the sensor data and threshold display area 3816. Bydisplaying the rain trip indicator 3842, the interface unit conveys thata rain event is occurring. The temperature indicator 3844 depicts thesensed temperature to be below the temperature threshold 3846. Inresponse, the interface unit displays the temperature trip indicator3848 to indicate a freeze condition has occurred.

Since the interface unit is in bypass rain/freeze mode 4506, even thoughthe interface unit has determined both a rain event and freeze conditionhas occurred, the interface unit does not interrupt the irrigationschedule of the irrigation controller 30. The interface unit returns tonormal irrigation mode 4502 when either the rain event and freezecondition has passed, the user manually returns the interface unit tonormal irrigation mode 4502 by pressing the irrigation button 3804, orafter a given time span, typically three days or seventy-two hours.

FIG. 53 illustrates an embodiment of the display screen of the interfaceunit when the interface unit is in the halt irrigation mode 4508 and thesensed rainfall is below the rainfall threshold 3840 and the sensedtemperature is above the temperature threshold 3846, corresponding tofair weather conditions. No dark horizontal bars fill the rainfallindicator 3838, indicating the sensor unit has not sensed any rainfallor moisture. For this example, since there is no sensed rainfall, thesensed rainfall falls below the rainfall threshold 3840 and the area ofthe display screen 3810 which normally displays the rain trip indicator3842 is empty. The temperature indicator 3844 depicts the sensedtemperature to be above the temperature threshold 3846, therefore thearea of the display screen 3810 which normally displays the temperaturetrip indicator 3848 is empty.

Since the interface unit is in the halt irrigation mode 4508, theinterface unit interrupts the irrigation schedule of the irrigationcontroller 30, regardless of the sensed weather conditions. The displayscreen 3810 in FIG. 53 indicates fair weather conditions which wouldnormally prompt normal irrigation. However, the user may wish tointerrupt irrigation for an event such as an outdoor gathering andtherefore has the option to choose the halt irrigation mode 4508 tointerrupt irrigation regardless of the sensed weather conditions. Theinterface unit returns to normal irrigation mode 4502 either when theuser manually places the interface unit into normal irrigation mode 4502as discussed above or after a given time span, typically three days orseventy-two hours.

FIGS. 54-57 illustrate an embodiment of the display screen 3810 of theinterface unit during light rain. During the light rain, rainfall hasbeen sensed, however, the amount of rainfall sensed and displayed on therainfall indicator 3838 never exceeds the set rainfall threshold 3840.As illustrated in FIGS. 54-57, as the sensed rainfall displayed on therainfall indicator 3838 increases, the interface determines a rain eventhas occurred and interrupts irrigation. In an alternative embodiment,the interface unit waits to interrupt irrigation until the rainfallthreshold 3840 has been met or exceeded before irrigation isinterrupted. When the rain sensor system begins to dry, the interfaceunit returns to the normal irrigation mode 4502 and allows theirrigation controller 30 to irrigate. For FIGS. 54-57, the temperatureis above the temperature threshold 3846, and therefore a freezecondition has not been determined and the temperature trip indicator3848 is not displayed on the display screen 3810.

At the beginning of the light rain, as depicted in FIG. 54, rainfall isincreasing and the dark horizontal bars within the rainfall indicator3838 gradually fills the rainfall indicator 3838. Even though the sensedrainfall is below the rainfall threshold 3840, the interface unit hasdetermined a rain event is occurring since the sensed rainfall, or themoisture in the system, is increasing. The rain trip indicator 3842 isthen displayed onto the display screen 3810 to indicate a rain event isoccurring. The interface unit proceeds to interrupt irrigation, and thehalt irrigation mode 4508 is displayed on the display screen 3810 in theirrigation mode display area 3814. In FIG. 55, the sensed rainfall isstill increasing, the dark horizontal bars within the rainfall indicator3838 fills the rainfall indicator 3838 more than what is illustrated inFIG. 54.

As the rain continues, moisture in the system increases but neverexceeds the rainfall threshold 3840. As depicted in FIG. 56, as therainfall sensed and displayed in the rainfall indicator 3838 reaches therainfall threshold 3840 and begins to dry out, the interface unitreturns to the normal irrigation mode 4502. As the system further driesout, the moisture in the system decreases and therefore the amount ofthe rainfall indicator 3838 filled by dark horizontal bars decreases asdepicted in FIG. 57.

FIGS. 58-63 illustrate an embodiment of the display screen 3810 of theinterface unit when the interface unit is undergoing a hard rain. Duringhard rain, the amount of rainfall sensed by the sensor unit exceeds therainfall threshold 3840. As illustrated in FIGS. 58-63, as the sensedrainfall displayed on the rainfall indicator 3838 increases, theinterface determines a rain event has occurred and interruptsirrigation. When the rain sensor system begins to dry, the interfaceunit returns to normal irrigation mode 4502 and allows the irrigationcontroller 30 to irrigate. For FIGS. 54-63, the temperature is above thetemperature threshold 3846, and therefore a freeze condition has notbeen determined and the temperature trip indicator 3848 is not displayedon the display screen 3810.

At the beginning of hard rain, as depicted in FIG. 58, rainfall isincreasing and the dark horizontal bars within the rainfall indicator3838 gradually fills the rainfall indicator 3838. Even though the sensedrainfall is below the rainfall threshold 3840, the interface unit hasdetermined a rain event is occurring since the sensed rainfall, or themoisture in the system, is increasing. The rain trip indicator 3842 isthen displayed onto the display screen 3810 to indicate a rain event isoccurring. The interface unit proceeds to interrupt irrigation, and thehalt irrigation mode 4508 is displayed on the display screen 3810 in theirrigation mode display area 3814. As the hard rain continues, rainfallis still increasing and the moisture sensed in the system has exceededthe rainfall threshold 3840. FIG. 59 illustrates the increasing rainfallas the dark horizontal bars fill the rainfall indicator 3838 past therainfall threshold 3840. The rain trip indicator 3842 is still displayedon the display screen 3810 and the interface unit continues in haltirrigation mode 4508.

FIG. 60 illustrates hard rain when the amount of moisture sensed fillsthe rainfall indicator 3838. At this point, the interface unit continuesin the halt irrigation mode 4508. FIG. 61 illustrates the rain sensorsystem as the system begins to dry and the amount of moisture senseddecreases. The rainfall indicator 3838 is less filled than the rainfallindicator 3838 of FIG. 60, however, the rain sensed in FIG. 61 is stillabove the rainfall threshold 3849 and therefore the rain trip indicator3842 is displayed on the display screen 3810 and the interface unitcontinues in halt irrigation mode 4508. FIG. 62 depicts the portion ofthe hard simulation when the sensor unit has dried to the point wherethe rainfall/moisture sensed in the system is less than the rainfallthreshold 3840. At this point, the interface unit detects the end of therain event and returns to normal irrigation mode 4502. In oneembodiment, the interface unit detects the end of the rain event whenthe rainfall/moisture sensed in the system has decreased to the rainfallthreshold 3840. In another embodiment, the interface unit detects theend of the rain event when the rainfall/moisture sensed in the systemhas decreased to a point below the rainfall threshold 3840. FIG. 63depicts further drying of the rain sensor system, the rainfall indicator3838 has fallen much lower than the rainfall threshold 3840 and theinterface unit continues in normal irrigation mode 4502.

FIGS. 64-69 illustrate an embodiment of the display screen 3810 of theinterface unit when the interface unit is undergoing a night freeze(e.g., more broadly characterized as a low temperature event). Duringnight freeze, the temperature sensed drops to the freezing point(roughly thirty-two degrees Fahrenheit). As illustrated in FIGS. 64-49,the temperature decreases below the temperature threshold 3846, thenfurther decreases to the freezing point to trigger the low temperatureindicator 3850. Once the temperature drops below the temperaturethreshold 3846, a freeze condition is determined and the interface unitproceeds to interrupt irrigation of the irrigation controller 30. Oncethe temperature has increased above the temperature threshold 3846, thefreeze condition has ended and the interface unit returns to normalirrigation mode 4502. For FIGS. 64-69, no moisture is sensed in the rainsensor system and therefore the rain trip indicator 3842 is not presenton the display screen 3810.

At the beginning of night freeze, as depicted in FIG. 64, the sensedtemperature displayed by the temperature indicator 3844 is above thetemperature threshold 3846. No freeze condition has been determined bythe interface unit and therefore the interface unit is in normalirrigation mode 4502 and does not interrupt the watering schedule of theirrigation controller 30. At FIG. 65, the temperature displayed on thetemperature indicator 3844 is still above the temperature threshold3846. Accordingly, the interface unit continues in normal irrigationmode 4502.

As the temperature continues to drop, as depicted in FIG. 66, the sensedtemperature displayed by the temperature indicator 3844 drops below thetemperature threshold 3846. The interface unit determines that a lowtemperature (e.g., freeze) condition exists since the temperature hasdropped below the temperature threshold 3846. The temperature tripindicator 3848 is then displayed on the display screen 3810 to indicatea freeze condition is present. The interface unit proceeds to interruptirrigation, and the halt irrigation mode 4508 is displayed on thedisplay screen 3810 in the irrigation mode display area 3814. Thetemperature continues to drop until it has reached the freezing point.FIG. 67 illustrates one embodiment of the display screen 3810 once thesensed temperature has reached the freezing point. The low temperatureindicator 3850 is displayed within the temperature indicator 3844 andthe interface unit continues halt irrigation mode 4508.

FIG. 68 illustrates the display screen 3810 as the temperature begins toincrease from the freezing point. The low temperature indicator 3850 hasdisappeared, however the temperature is still below the temperaturethreshold 3846 and therefore a freeze condition still exists. Theinterface unit continues in halt irrigation mode 4508. After a givenamount of time, as depicted in FIG. 69, the temperature displayed by thetemperature indicator 3844 has risen above the temperature threshold3846. The interface unit has then detected the end of the freezecondition and switches to normal irrigation mode 4502, allowing theirrigation controller to proceed with normal watering functions.

Generally, the user interface is implemented under control of thecontroller 414 (see FIG. 37). The controller 414 receives inputs via theuser input 424 and sensor inputs from the sensor unit 12 via thetransceiver 412. Based at least in part on one or more inputs and/or onthe execution of one or more routines by the controller 414, thecontroller determines what to cause the display unit 3704 to display tothe viewer and/or whether the current display is to be updated. Forexample, display generating and/or updating may be based in part on: (1)user inputs, such as, user manipulation of the various buttons 3604,3606, 3608 and 3610; (2) sensor data from the sensor unit 12, such asrainfall measurements, temperature measurements, battery strengthindications, pairing communications, signal strength indications, and soon; (3) information sent to the sensor unit from the interface unit viathe transceiver, such as pairing and setup communications, queries, andso on; and (4) routines executed by the processing unit 3716 of thecontroller 414, such as irrigation interrupt, pairing, setup routines,to name a few.

In order to cause particular information to be displayed via the displayunit 3704 (for example, via visual representations of data such as iconsor other visual indicators), the processing unit 3716 determines whatinformation is to be displayed via the user display 3706. Next, theappropriate signal/s are generated and transmitted to the displaydriver/s 3708. It is noted that the display driver/s 3708 may beimplemented as one or more units, some or all of which may beimplemented functionally or structurally within the controller 414. Thenthe display driver/s 3708 generates the appropriate display drivingsignals which are sent to the user display 3706. The user display 3706responds to the driving signals by displaying information to the user.As described herein the user display 3706 may be provided as one or moreof a display screen (e.g., a dot matrix-type liquid crystal display(LCD) (color or black/white), a segment-type LCD (color or black/white),a cathode ray tube (CRT) (color or black/white), a plasma display panel(PDP) (color or black/white)), one or more illuminatable devices (e.g.,light emitting diodes (LEDs)) of one or more colors, or similar displaydevices, or combinations thereof.

FIG. 70 is an illustration of another embodiment of an interface unit7000 for use in the rain sensor system 10 of at least FIGS. 1 and 2,which is similar to the interface units of FIGS. 4 and 37. In thisembodiment, the interface unit 7000 comprises a housing 7002, a display7012 and a user input. The user input comprises a forward or right arrow(“→”) button 7004, a back or left arrow (“←”) button 7006, a plus (“+”)button 7008, a minus (“−”) button 7010, and/or other such buttons. Inaccordance with several embodiments, the interface unit 7000 ispositioned near the controller 30 and couples to one or more of theactivation lines 32 or common line 34 from the irrigation controller 30or an interface 38 (e.g., a sensor input) or common connection point atthe irrigation controller 30 (not shown in FIG. 70). The interface unit7000 wirelessly communicates with one or more sensor units 12. Inoperation, the interface unit 7000 receives one or both of sensedrainfall (e.g., measurement of accumulated rainfall) and temperatureinformation and/or measurements and determines whether irrigation, to beexecuted by the irrigation controller 30, should be allowed orinterrupted. The operation of the interface unit 7000 is similar to thatdescribed for the embodiments of at least FIGS. 4, 7A-B, 8, 36 and 37.

Referring next to FIG. 71A, an embodiment is shown of a graphical userinterface 7110 displayed on the display 7012 of the interface unit 7000of FIG. 70, displaying a graphical user interface that displays variousicons, graphical representations, pictorial representations and/or otherrepresentations, or visual indications that may be displayed at giventimes on the display 7012. The displayed graphical user interface andpictorial representations are further described in related U.S. DesignPat. No. D623,194, issued Sep. 7, 2010, to Carl D. Cook et al., entitledGRAPHICAL USER INTERFACE FOR A WIRELESS RAIN SENSOR, which isincorporated in its entirety herein by reference; and to U.S. Designpatent application No. 29/366,882, filed Jul. 30, 2010, for Carl D. Cooket al., entitled WIRELESS RAIN SENSOR WITH A GRAPHICAL USER INTERFACE,which is incorporated in its entirety herein by reference. It is notedthat in some embodiments the interface unit 7000 can similarly beimplemented into an irrigation controller, and/or located on or integralto the irrigation controller. For example, an interface module can beincorporated into an irrigation controller and/or the functionality ofthe various icons, graphical representations, pictorial representationsand/or other representations, or visual indicators can similarly bedisplayed on a display of an irrigation controller that incorporates thefunctionality of the interface unit 7000 (e.g., on the display 3302 ofthe irrigation controller 3300).

The representations in FIG. 71A are used to convey information to theuser, and the combinations of two or more representations simultaneouslydisplayed convey information at least about irrigation interruption,reasons why irrigation was interrupted, states or modes of operation ofthe interface unit and/or irrigation, and other such information. It isnoted that not all of the pictorial representations are required to bedisplayed at a single time, and typically less than all the pictorialrepresentations would be displayed at a single time. In some cases,pictorial representations may be displayed sequentially to conveyinformation. Further, some embodiments may be configured such that theinterface unit can enter a sleep mode where the display is effectivelypowered down and none of the pictorial representations are displayed,which may be initiated after a threshold amount of time following a mostrecent user interaction with the interface unit. The display 7012 canquickly reactivate from the sleep mode in response to user interaction(e.g., user pressing one or more of the buttons). Again, the interfaceunit communicates with one or more sensor units, where the communicationcan be via wired or wireless communication, and further interfaces withan irrigation controller 30 to at least in part provide some controlover the irrigation.

In some embodiments, the displayed pictorial representations can includea battery remaining indicator 7118, a signal strength indicator 7120, asensor unit indicator 7126, an irrigation device (e.g., a rotor)indicator or representation 7128, sprayed water indicator 7130, aninterrupt or suspend indicator 7132, a bypass or override indicator7134, a rain or rainfall indicator 7138, an indicator of rainfallthreshold or rainfall threshold parameter 7140, a rain symbol or raintrip indicator 7142, a temperature indicator 7144, an indicator oftemperature threshold or temperature threshold parameter 7146, atemperature trip indicator 7148 and/or other such representations. Thebattery remaining indicator 7118, the signal strength indicator 7120 andthe sensor unit indicator 7126 together are sometimes referred to asand/or are grouped within a pairing status or sensor indicator 7127.

The battery remaining indicator 7118 displays the strength of thebattery of a sensor unit 12 in communication with the interface unit7000. In some instances, the battery remaining indicator 7118 is filledwith a varying number of bars that indicate battery strength. When thebattery remaining indicator 7118 is completely filled with bars, thenthe battery of the sensor unit is at about full strength. As the batterystrength of the sensor unit 12 depletes, the battery remaining indicator7118 will display fewer bars. The number of bars displayed within thebattery remaining indicator 7118 roughly corresponds to the amount ofbattery strength left in the sensor unit. For example, in one embodimentthe battery remaining indicator 7118 is filled with four bars when thebattery strength of the sensor unit is at about its maximum capacity.When the battery strength of the sensor unit is roughly at halfstrength, then the battery remaining indicator 7118 would be show twobars. Once the battery remaining indicator 7118 is depicted with eitherone or no bars, this should signal to a user to change the battery ofthe given sensor unit. As described herein, the sensor unit 12 isconfigured to send information about its battery strength to theinterface unit. In other embodiments, the battery indicator 7118 isdepicted with another indicator, such as a fill level of a batteryrepresentation, a bar with a sliding indicator or other such indicationof battery power at the corresponding sensor unit.

The signal strength indicator 7120 illustrates the strength of signalingvia the communication link between the communicating interface unit andsensor unit. In one embodiment, the signal strength indicator 7120illustrates the strength of a radio signal (e.g., in terms of signal tonoise) between the interface unit (14, 3600, 3702, 7000) and a givensensor unit 12. The signal strength indicator 7120 comprises a pluralityof bars of increasing heights. The number of bars represents thestrength of the signals received from the sensor unit at the interfaceunit.

The sensor unit indicator 7126 conveys to the user which sensor unit 12the interface unit 14 is currently communicating with. In FIG. 71A, thesensor unit indicator 7126 is show with four identifying numbers (i.e.,“1,” “2,” “3” and “4”). Typically, one of the indicator numbers is shownat any given time, such that the battery remaining indicator 7118 andsignal strength indicator 7120 correspond to the sensor unit identifiedby the sensor unit indicator 7126. In some embodiments, the sensor unitindicator 7126 toggles between substantially any number of sensor unitsin communication with the interface unit, where the sensor numbers ofthe sensor unit indicator 7126 identifies the sensor unit correspondingto the displayed battery remaining indicator 7118 and signal strengthindicator 7120.

The rainfall indicator 7138 illustrates the amount of moisture currentlypresent at or sensed by the sensor unit 12. In some instances, therainfall indicator 7138 displays a graphical representation comprisingone or more displayed bars dependent on the amount of accumulatedrainfall with an greater number of bars being displayed as the sensedaccumulated amount of rainfall increases. In some embodiments, therainfall indicator 7138 fills with horizontal bars as rainfall iscollected at the sensor unit and the level of rainfall is communicatedto the interface unit 14. The rain trip indicator 7142 is exemplified asa rain cloud which appears when the interface unit determines that themoisture sensed by a given sensor unit has risen above the rainfallthreshold 7140, or as a result of increasing rainfall as describedabove.

The rainfall threshold 7140 is exemplified as an arrow that can bemoved, toggled or otherwise adjusted up and down the height of therainfall indicator 7138. In some instances, the rainfall threshold 7140can be selected from a plurality of predefined amounts of moisture. Inother implementations, the threshold may be on a sliding scale, a usercan select specific numbers by using the buttons, or other suchdesignations. For example, a user can utilizes the forward button 7004,the backward button 7006, the plus button 7008 and the minus button 7010of the user interface to set the rainfall threshold 7140, indicating athreshold level of rainfall typically triggering the interface unit 14to interrupt irrigation. The embodiment depicted in FIG. 71 shows sixpredefined moisture threshold levels. Again, however, more or fewerpredefined threshold levels can be available, a sliding scale may beprovided, a user may enter a selected value, or the like. Additionallyor alternatively, a user may select or specify a range and thepredefined thresholds could automatically be defined within that rangebased on the size of the range (e.g., equally distributed over thescale).

The rainfall threshold 7140 displays to the user the selected rainfallthreshold point with respect to the rainfall indicator 7138. In someembodiments, as the user presses the plus button 7008, the rainfallthreshold 7140 is raised along the rainfall indicator 7138. In someimplementations, once the rainfall threshold 7140 reaches the top of therainfall indicator 7138 further depression of the plus button 7008 cancause the rainfall threshold 7140 to wrap to the bottom of the rainfallindicator 7138 and repeat as above. Similarly, continued selection ofthe minus button 7010 in some embodiments can cause the rainfallthreshold 7140 to wrap around to the top of the rainfall indicator 7138.When the rainfall threshold 7140 is closer to the top of the rainfallindicator 7138, the user has selected a high rainfall threshold pointallowing the irrigation controller to continue irrigation even though,in some instances and/or configurations, a relatively high level ofmoisture may be detected. As introduced above, in other implementationsa user can set the rainfall threshold 7140 by selecting specific numbersby using the buttons (e.g., numbers are displayed and changed inresponse to a selection of the plus or minus button, such asincrementing a predefined amount of rainfall, for example 0.05 inches,with each selection of the plus or minus button). Similarly, in someinstances, numeric values of the rainfall threshold 7140 and/or thesensed accumulation amount of rainfall in the rainfall indicator 7138can be displayed in cooperation with or in place of the rainfallindicator 7138, such as in response to a selection of a pattern of thebuttons.

The temperature indicator 7144 illustrates the temperature currentlypresent in the rain sensor system as measured by the sensor unit 12identified by the sensor unit indicator 7126. In the embodiment of FIG.71A, the temperature indicator 7144 is exemplified as a thermometer; theamount of fill in the thermometer illustrates the sensed temperature.Disposed to the side of the temperature indicator 7144 is thetemperature threshold 7146. The temperature threshold 7146 illustratesthe selected sensitivity for interrupted irrigation during lowtemperature. The temperature trip indicator 7148 is exemplified as asnowflake which appears on the display 7012 when the interface unitdetermines from measurements sent from the sensor unit that thetemperature has dropped below the temperature threshold 7146.

In some embodiments the temperature threshold 7146 is exemplified as anarrow that can be moved, toggled or otherwise adjusted up and down theheight of the temperature indicator 7144. In some instances, thetemperature threshold 7146 can be selected from a plurality ofpredefined temperatures. In other implementations, the threshold may beon a sliding scale, a user can select specific temperature by using thebuttons, or other such designations. The embodiment depicted in FIG. 71Ashows three predefined temperature threshold levels. Again, however,more or fewer predefined threshold levels can be available, a slidingscale may be provided, a user may enter a selected value, or the like.Additionally or alternatively, a user may select or specify a range andthe predefined thresholds could automatically be defined within thatrange based on the size of the range (e.g., equally distributed over thescale). Typically, the temperature threshold 7146 indicates a minimumsensed temperature that would prompt the interface unit to interruptirrigation. The temperature threshold 7146 displays to the user theselected temperature threshold point with respect to the temperatureindicator 7144.

Similar to the rainfall threshold, in some embodiments, the user maypress the plus button 7008 or minus button 7010 to alter the temperaturethreshold 7146. In some embodiments, once the temperature threshold 7146reaches the top of the temperature indicator 7144 further depression ofthe plus button 7008 can cause the temperature threshold 7146 to wrapback to the bottom of the temperature indicator 7144 and repeat asabove; and similarly further selection of the minus button 7010 when thetemperature threshold 7146 is at a bottom of the temperature indicator7144 can cause the temperature threshold 7146 to wrap to the top of thetemperature indicator 7144. In other implementations, the temperaturethreshold 7146 may be selected from specific numbers by using thebuttons (e.g., numbers are displayed and changed in response toselection of the plus or minus button, such as incrementing a predefinedamount of temperature, for example a 0.5° F., in response each selectionof the plus or minus button). Similarly, in some instances, a numericvalue of the temperature threshold 7146 and/or the sensed temperaturecan be displayed in association with or in place of the temperatureindicator 7144, such as in response to a selection of a pattern of thebuttons.

The irrigation device indicator 7128 and sprayed water indicator 7130displayed together indicate to a user that irrigation is authorizedand/or active. The interrupt indicator 7132 identifies that theirrigation is interrupted. Typically, while the interrupt indicator 7132is displayed the sprayed water indicator 7130 is not displayed furtherconveying to a user that irrigation is interrupted. Some of the otherpictorial representations may be displayed in cooperation with theinterrupt indicator 7132 to further identify to the user the reasoningfor the irrigation interruption. For example, the display of theinterrupt indicator 3732 while the rain trip indicator 7142 is displayedidentifies that the irrigation is interrupted due at least to an amountof rainfall exceeding the rainfall threshold 3440 or that the sensedrainfall, although not above the rainfall threshold 3440, is increasingand the interface unit determines a rain event has occurred andinterrupts irrigation. Similarly, the display of the interrupt indicator3732 while the temperature trip indicator 7148 is displayed identifiesthat the irrigation is interrupted due at least to the temperaturefalling below the temperature threshold 7146.

The override indicator 7134 identifies when a user has selected tobypass one or more of the thresholds and sensed weather conditions, orwhen a user manually overrides irrigation to force an interruptregardless of the temperature and/or rainfall. Again, one or more otherpictorial representations displayed while the override indicator 7134 isdisplayed can provide the user with the information to accuratelyinterpret the override or bypass. For example, displaying the overrideindicator 7134 while the interrupt indicator 7132 is displayed and thesprayed water indicator 7130 is not displayed identifies that theinterface unit is in the override interrupt or halt irrigation mode 4508and that a user is intentionally interrupting irrigation. Typically,because the interface unit is in the halt irrigation mode 4508, theinterface unit interrupts the irrigation schedule of the irrigationcontroller 30 regardless of the sensed weather or other environmentalconditions. This mode, as described above, may be used by the user tointerrupt irrigation, such as for an event (e.g., an outdoor gathering)and therefore has the option to choose the halt irrigation mode 4508.The interface unit returns to normal irrigation mode 4502 when the usermanually places the interface unit into normal irrigation mode 4502 asdiscussed above, or in some instances automatically, such as after agiven time span. The time span can be substantially any time span. Insome embodiments, the time span may be predefined (e.g., three days orseventy-two hours), while in other instances, the time span may be userselected (e.g., from a list of predefined time spans), or the time spanmay be user definable. Additionally, in some implementations, theoverride indicator 7134 may specify the time span (e.g., “72 hr”) and/ormay count down the remainder of a time span.

Similarly, displaying the override indicator 7134 while the sprayedwater indicator 7130 is displayed and the interrupt indicator 7132 isnot displayed identifies that the interface unit is in the bypass rainmode 4504 or bypass rain/freeze mode 4506 and further conveys that auser desires to intentionally continue to irrigate regardless of anamount of sensed rainfall and/or sensed temperature. As described above,during the bypass rain mode 4504 or bypass rain/freeze mode 4506, theinterface unit allows the irrigation controller to irrigate during fairweather, rain, and/or when a low temperature condition (e.g., a freezecondition) is determined.

The interface unit returns to the normal irrigation mode 4502 when theuser manually returns the interface unit to normal irrigation mode 4502(e.g., using the right arrow button 7004 and/or left arrow button 7006to select the irrigation device indicator 7128 in a program or set-upmode, and then using the plus button 7008 and/or minus button 7010 tothe normal irrigation mode 4502 to allow irrigation), or in someinstances automatically after a given time span. This time span can besubstantially any time span. In some embodiments, the time span may bepredefined (e.g., three days or seventy-two hours), while in otherinstances, the time span may be user selected (e.g., from a list ofpredefined time spans), or the time span may be user defined.Additionally, in some implementations, the override indicator 7134 mayspecify the time span (e.g., “72 hr”) and/or may count down theremainder of a time span. In some implementations, once the interfaceunit has determined a freeze condition has passed (e.g., when the sensedtemperature has risen above the temperature threshold 7146) and/or theinterface unit has determined the rain event has passed (e.g., when thesensed rainfall in the rainfall indicator 7138 has fallen below therainfall threshold 7140), the interface unit returns to the normalirrigation mode 4502.

While the interface unit is in the bypass rain mode 4504 or bypassrain/freeze mode 4506 the interface unit typically continues to displaythe rainfall indicator 7138 showing the amount of moisture measured bythe sensor unit 12 and displays the temperature indicator 7144 showingthe temperature as measured by the sensor unit 12. Further, in someinstances, the rain trip indicator 7142 and/or the temperature tripindicator 7148 can also be displayed in those instances where theinterface unit determines that the moisture amount exceeds the rainfallthreshold 7140 and/or the temperature falls below the temperaturethreshold 7146. The levels identified by the rainfall indicator 7138 andthe temperature indicator 7144, as well as the rain trip indicator 7142and/or the temperature trip indicator 7148, continue to allow theinterface unit to convey relevant information to a user, including atleast whether a rain event is occurring and/or a freeze condition isdetected. Again, while in the bypass rain mode 4504 the interface unitdoes not interrupt the irrigation schedule of the irrigation controller30 even though the interface unit may have determined that a rain eventhas occurred, in the bypass rain/freeze mode 4506 the interface unitdoes not interrupt the irrigation schedule of the irrigation controller30 even though the interface unit may have determined that a rain eventand/or freeze condition has occurred.

FIG. 71B illustrates a graphical user interface 7111 displayed on thedisplay 7012 of the interface unit 7000 of FIG. 70 according to someembodiments. The graphical user interface 7111 is similar to thegraphical user interface 7110 of FIG. 71A, but does not display thesensor unit indicator 7126. In some embodiments, the interface unit 7000only communicates with a single sensor unit 12 and/or may be configuredto only communicate with a single sensor unit. As such, the graphicaluser interface 7111 may be configured to not display the sensor unitindicator 7126 because the interface unit 7000 communicates with thesingle sensor unit 12.

FIG. 71C illustrates a graphical user interface 7112 displayed on thedisplay 7012 of the interface unit 7000 of FIG. 70 according to someembodiments. The graphical user interface 7112 is similar to thegraphical user interface 7110 of FIG. 71A, but does not display thetemperature indicator 7144 or corresponding temperature threshold 7146.In some embodiments, the interface unit 7000 provides irrigation controlrelative to sensed rainfall and does not consider temperature, displayinformation about temperature or interrupt irrigation based ontemperature. Accordingly, the graphical user interface 7112 does notdisplay the temperature indicator 7144 or corresponding temperaturethreshold 7146, and further does not display the temperature tripindicator 7148 as the interface unit 7000 in such a configuration doesnot interrupt irrigation based on temperature and would not display thetemperature trip indicator 7148. Additionally, in some embodiments thegraphical user interface 7112 does not display the sensor unit indicator7126. As described above, the interface unit 7000 may be communicatingwith a single sensor unit and/or be configured to only communicate witha single sensor unit 12. As such, the graphical user interface 7112 maynot display the sensor unit indicator 7126.

In yet other embodiments, the interface unit may only interruptirrigation based on temperature. In these such embodiments, thetemperature indicator 7144, the corresponding temperature threshold 7146and the temperature trip indicator 7148 may only be displayed, while therainfall indicator 7138, corresponding rainfall threshold 7140 and therain trip indicator 7142 are not displayed when the interface unit 7000is configured to interrupt irrigation based on temperature and notconfigured to interrupt irrigation based on rain fall.

In FIG. 72, an embodiment is shown of the display 7012 of the interfaceunit 7000 of FIG. 70 displaying an initial power up or initialactivation screen or view 7200. In the power up screen 7200 the pairingstatus indicator 7127 is shown with the battery remaining indicator 7118without an indication of a battery level and the signal strengthindicator 7120 without an indication of signal strength. Further, thetemperature indicator 7144 and rainfall indicator 7138 are shown, againwithout an indication of a measured temperature or an amount of moisturedetected. Also shown is the irrigation device indicator 7128 without thesprayed water indicator 7130, the interrupt indicator 7132 or theoverride indicator 7134. From this power up screen 7200 a user canconfigure the interface unit through the use of the interface buttons totransition between the pairing status indicator 7127 to initiate andestablish a connection with one or more sensor units 12, the temperatureindicator 7144 to select a temperature threshold 7146, the rainfallindicator 7138 to select a rainfall threshold 7140, and the irrigationdevice indicator 7128 to allow the user to force an interrupt and/or toactivate the override condition. For example, the user can select theright arrow button 7004 to transition to the pairing status indicator7127 and activate a pairing with one or more sensor units (e.g.,pressing both the left arrow button 7006 and the right arrow button 7004together while the pairing status indicator 7127 is highlighted toactivate the interface unit to transmit a connection signal). In someinstances, the battery remaining indicator 7118, the signal strengthindicator 7120, the sensor unit indicator 7126 and/or the pairing statusindicator 7127 may flash while the user is configuring the pairing ofthe interface unit with one or more sensor units.

Similarly, while in the power up screen 7200 the user can further selectthe right arrow button 7004 to transition from the pairing statusindicator 7127 to the temperature indicator 7144 to configure thetemperature indicator and/or select a temperature threshold 7146 (e.g.,using the plus button 7008 and/or minus button 7010 to select a desiredtemperature threshold 7146). Again, in some instances the temperatureindicator 7144 may flash while the user is configuring the temperatureindicator and/or selecting a temperature threshold 7146). By againselect the right arrow button 7004 the user can cause a transition tothe rainfall indicator 7138 to allow the user to configure the rainfallindicator 7138 and/or select a rainfall threshold 7140 (e.g., using theplus button 7008 and/or minus button 7010 to select a desired rainfallthreshold 7140). Again, in some instances the rainfall indicator 7138may flash while the user is configuring the rainfall indicator 7138and/or selecting a rainfall threshold 7140). A further selection of theright arrow button 7004 can cause a transition to the irrigation deviceindicator 7128. The use of the plus button 7008 and/or minus button 7010can allow the user to transition between predefined configurations forthe irrigation device indicator 7128 (e.g., normal irrigation mode 4502to allow irrigation, halt irrigation mode 4508 to suspend irrigation,suspend irrigation for a period of time (e.g., 24 hr, 48 hr, 72 hr,etc), sensor override to allow for continued irrigation, sensor overridefor a defined period of time (e.g., bypass rain mode 4504, bypass freezemode, bypass rain/freeze mode 4506, or the like), and/or other suchmodes. Other settings, parameters, conditions and/or otherconfigurations can be defined through further transitions.

FIG. 73 illustrates an embodiment of the display 7012 of the userinterface of FIG. 70 when the system is pairing with a sensor unit(e.g., rain sensor device) to establish a communication link. Thedisplay 7012 shows that no rainfall or temperature data has yet to besensed for the sensor unit that the interface unit 14 is attempting topair with. To begin the pairing of the interface unit with a givensensor unit, the user in some instances presses one or more of thebuttons on the interface unit. For example, the user can press both theright arrow button 7004 and the left arrow button 7006 simultaneously,and in some instances pressing the buttons for a predefined period oftime. In some embodiments, the predefined period of time is greater than2 seconds (e.g., about 5 seconds). In response the interface unit 14initiates the transmission of a pairing signal.

In some instances, while the sensor unit and the interface unit arepairing, the signal strength indicator 7120 may blink or otherwiseindicate that pairing is taking place. Further, with someimplementations the display 7012 identifies a sensor unit number in thesensor unit indicator 7126. As described above and further below, someembodiments allow an interface unit to communicate with multiplesensors. For this example, the sensor unit indicator 7126 in FIG. 73 isset to “1,” such as in a first time the interface unit is pairing with asensor unit. It should be appreciated that the sensor unit indicator7126 may be set to a different number, corresponding to a differentsensor unit. In some instances the sensor unit indicator 7126 may flashto further highlight the sensor unit number. Similarly, the batteryremaining indicator 7118, the signal strength indicator 7120 and/or thepairing status indicator 7127 may flash. The some instances otherindications may demonstrate that pairing is being performed, such assequentially flashing the individual bars within the signal strengthindicator 7120 or some other indication. In many embodiments, however,the interface unit may pair with one sensor unit, or may be configuredto only be capable of pairing with a single sensor unit, and duringpairing and/or during operation the sensor unit indicator 7126 is notdisplayed. In some embodiments, once an interface unit is paired with asensor unit, the pairing is maintained at one or both of the interfaceunit and the sensor unit, and may even be maintained after a poweroutage. Similarly, in some implementations, the user set thresholdsand/or parameters may also be maintained even in the event of a poweroutage.

As described above, in some embodiments the sensor unit can be equippedwith a lighting mechanism to communicate to the user the signal strengthbetween the sensor unit and the interface unit to help determine theoptimal location for the sensor unit. For example, the sensor unit mayutilize a lighting mechanism to represent signal strength, such asthrough a series of blinks with the larger the number of blinksidentifying greater signal strength.

Once the pairing is complete and the interface unit has paired with thesensor unit, the display screen 7012 displays the battery remainingindicator 7118, the signal strength indicator 7120 and the sensor unitindicator 7126 for the paired sensor unit. This display indicates to theuser that pairing was successful. In some implementations, the displayedpairing status indicator 7127 may eventually disappear in a specifiedamount of time or in response to further user interaction, such as atransition to a different state such as a transition to configure one ormore thresholds, setting an override or the like. In some instances, theinterface unit transitions to an irrigation mode (e.g., normalirrigation mode 4502) when the pairing is complete, unless one or moreother user inactions cause a transition to another mode.

FIG. 74 illustrates one embodiment of the display 7012 of the userinterface of FIG. 70 once the interface unit has been paired to one ormore rain sensor devices, and the system is in normal irrigation mode.In FIG. 74, the display displays a combination of icons orrepresentations that convey to the user that the interface unit is in anormal irrigation mode. In the example depicted in FIG. 74, rainfallindicator identifies that no precipitation (or less than a minimumthreshold amount of precipitation) has been sensed, and the temperatureindicator 7144 shows that the sensed temperature is above thetemperature threshold 7146. Again, this normal mode is entered when theinterface unit has determines that a rain event is not occurring and/orthe sensed moisture is below the rainfall threshold 7140, and the sensedtemperature is above the temperature threshold 7146. The rain tripindicator 7142 is not displayed because the amount of moisture does notexceed the rainfall threshold 7140 and/or a rain event has not beenidentified. Similarly, the temperature trip indicator 7148 is also notdisplayed because the temperature is above the temperature threshold7146.

When the interface unit is in the normal irrigation mode 4502, theinterface unit displays the pictorial representations of the irrigationdevice indicator 7128 and the sprayed water indicator 7130 identifyingto the user that the system is allowing irrigation as programmed throughthe irrigation controller 30. In some instances, while in the normalirrigation mode, the display 7012 further displays the rainfallindicator 7138, rainfall threshold 7140, the temperature indicator 7144and temperature threshold 7146. Further in some implementations, thesensor unit indicator 7126 along with the corresponding batteryremaining indicator 7118 and signal strength indicator 7120 may also bedisplayed.

During the normal irrigation mode 4502, the interface unit does notinterrupt the irrigation schedule of the irrigation controller 30, andallows the controller 30 to irrigate as it is programmed. The interfaceunit transitions from the normal irrigation mode 4502, which effectivelyshut off the normal irrigation mode, when the interface unit determinesthat the rainfall sensed is above the rainfall threshold 7140, detects arain event, determines that the sensed temperature has drops below thetemperature threshold 7146, or otherwise transitions from the normalirrigation mode (e.g., manual interrupt by the user). In someimplementations, the normal irrigation mode 4502 may be viewed as thedefault mode, where the system reverts back to the normal irrigationmode 4502, for example, after a given amount of time from one or more ofthe other modes of operation. When the interface unit reverts back tothe normal mode can depend on the mode the interface unit is in. Forexample, in some embodiments, the interface unit reverts from anoverride mode and back to the normal irrigation mode after a predefinedor user specified time (e.g., after 72 hours). As another example, theinterface unit reverts from an weather condition interrupt and back tothe normal irrigation mode after the interface unit determines the rainevent has ended, the moisture level drops below the rainfall threshold7140 (or drops a predefined amount below the rainfall threshold), and/orthe freeze condition no longer exists.

It is noted that in some embodiments, when the interface unit is in thenormal irrigation mode one or more of the battery remaining indicator7118, the signal strength indicator 7120, the sensor unit indicator7126, the pairing status indicator 7127, the rainfall indicator 7138,the rainfall threshold 7140, the temperature indicator 7144, and/or thetemperature threshold 7146 may not be displayed. For example, in someinstances only the irrigation device indicator 7128 and water sprayindicator 7130 may be displayed, which can indicate normal operation inthe normal irrigation mode. Additionally or alternatively, when thesensed temperature is above the temperature threshold 7146 thetemperature indicator 7144 and temperature threshold 7146 may not bedisplayed. Similarly, when sensed rain and/or moisture level does notindicate a rain event the rainfall indicator 7138 and rainfall threshold7140 may not be displayed. Further, when the battery remaining indicator7118 is not a concern (e.g., above a threshold) the battery remainingindicator 7118 may not be displayed, and when the signal strength withthe sensor unit is not a concern (e.g., above a signal strengththreshold) the signal strength indicator 7120 may not be displayed.Furthermore, when the battery remaining indicator 7118 and signalstrength indicator 7120 are not displayed the sensor unit indicator 7126and the pairing status indicator 7127 may not be displayed. The relevantpictorial representations that are not actively displayed, however, maybe displayed upon further user interaction with the interface unit.Additionally or alternatively, the display 7012 may transition to asleep mode as described above.

FIG. 75A illustrates an embodiment of the display 7012 of the interfaceunit when the sensed rainfall is above the rainfall threshold 7140 whilethe sensed temperature is above the temperature threshold 7146, wherethe combination of representations conveys to the user that theirrigation is interrupted. As shown in FIG. 75A, the fill level, whichin some instances is represented by one or more horizontal bars, withinthe rainfall indicator 7138 exceeds the rainfall threshold 7140. Inresponse to the sensed rainfall exceeding the rainfall threshold 7140,the rain trip indicator 7142 is displayed. By displaying the rain tripindicator 7142, the interface unit conveys that a rain event isoccurring. Alternatively or additionally, the interface unit maydetermine a rain event is occurring when the amount of sensed moistureis gradually increasing upward, which can be depicted by graduallydisplaying an increased number of horizontal bars within the rainfallindicator 7138, triggering the interface unit to display the rain tripindicator 7142. Again in this example, the temperature indicator 7144depicts the sensed temperature to be above the temperature threshold7146, therefore the temperature trip indicator 7148 is not displayed.

Since the interface unit has determined a rain event is occurring, theinterface unit transitions to the halt irrigation mode and interruptsthe irrigation of the irrigation controller 30. The interface unitadditionally displays the interrupt indicator 7132 while not displayingthe water spray indicator 7130 indicating to a user that the interfaceunit is inhibiting/interrupting irrigation. The interface unit, in someimplementations, returns to the normal irrigation mode when the rainfall sensed by the rainfall indicator 7138 falls below the rainfallthreshold 7140. In other embodiments, the interface unit returns to thenormal irrigation mode when the sensed moisture level falls below therainfall threshold 7140 by a predetermined and/or user specified amount.In some instances, the display 7012 may further display the batteryremaining indicator 7118, signal strength indicator 7120 and sensor unitindicator 7126. In other instances, however, the battery remainingindicator 7118, signal strength indicator 7120 and sensor unit indicator7126 may not be displayed.

FIG. 75B depicts the user interface displayed on the display 7012 of theinterface unit 7000, similar to that depicted in FIG. 75A, in accordancewith some embodiments. As described above, in some embodiments, theinterface unit 7000 provides irrigation control relative to sensedrainfall and does not consider temperature. In the embodiment depictedin FIG. 75B, the graphical user interface does not display thetemperature indicator 7144 or corresponding temperature threshold 7146.Again, in this example, the sensed rainfall exceeds the rainfallthreshold 7140 and as such the rain trip indicator 7142 is displayedindicating (in cooperation with the lack of the sprayed water indicator7130 representation) that irrigation is interrupted due to theaccumulated rain.

FIG. 76 illustrates an embodiment of the display 7012 of the interfaceunit when the sensed temperature falls below the temperature threshold7146 while the sensed rainfall is below the rainfall threshold 7140 anda rain event is not identified, where the combination of representationsconvey to the user that the irrigation is interrupted. As shown in FIG.76, the sensed temperature, which in some instances is represented byone or more bars, within the temperature indicator 7144 is below thetemperature threshold 7146. In response, the interface unit displays thetemperature trip indicator 7148. As such, the interface unit indisplaying the temperature trip indicator 7148 conveys that a freezecondition has been detected by the interface unit. It is noted that thefreeze condition as used herein may be broadly referred to as a lowtemperature condition. That is, the low temperature condition may notstrictly correspond to a freeze, but simply to a defined lowtemperature.

Since the interface unit has determined a freeze condition is occurring,the interface unit transitions to the halt irrigation mode andinterrupts the irrigation of the irrigation controller 30. The interfaceunit additionally displays the interrupt indicator 7132 while notdisplaying the water spray indicator 7130 identifying to a user that theinterface unit is inhibiting/interrupting irrigation. The interfaceunit, in some implementations, returns to the normal irrigation modewhen the temperature sensed by the temperature indicator 7144 risesabove the temperature threshold 7146. In some instances, the displayfurther displays the battery remaining indicator 7118, signal strengthindicator 7120 and sensor unit indicator 7126. In other instances,however, the battery remaining indicator 7118, signal strength indicator7120 and sensor unit indicator 7126 may not be displayed.

FIG. 77 illustrates an embodiment of the display 7012 of the interfaceunit when the sensed rainfall is above the rainfall threshold 7140 andthe sensed temperature falls below the temperature threshold 7146, wherethe combination of representations conveys to the user that theirrigation is interrupted. As shown in FIG. 77, the fill level withinthe rainfall indicator 7138 exceeds the rainfall threshold 7140 and thesensed temperature is below the temperature threshold 7146. In response,the interface unit displays both the rain trip indicator 7142 and thetemperature trip indicator 7148. By displaying the rain trip indicator7142 and the temperature trip indicator 7148, the interface unit conveysthat a rain event and a freeze condition are occurring.

In response to detecting that either the rain event or the freezecondition is occurring, the interface unit transitions to the haltirrigation mode and interrupts the irrigation of the irrigationcontroller 30. The interface unit additionally displays the interruptindicator 7132 while not displaying the water spray indicator 7130identifying to a user that the interface unit is inhibiting/interruptingirrigation. Typically, the interface unit stays in the halt irrigationmode until both the temperature sensed by the temperature indicator 7144rises above the temperature threshold 7146 and the sensed moisturelevel, as displayed by the rainfall indicator 7138, falls below therainfall threshold 7140 (or in some instances falls below the rainfallthreshold 7140 by a predetermined and/or user specified amount). Again,in some embodiments, the display further displays the battery remainingindicator 7118, signal strength indicator 7120 and sensor unit indicator7126. In other instances, however, the battery remaining indicator 7118,signal strength indicator 7120 and sensor unit indicator 7126 may not bedisplayed.

FIG. 78 illustrates an embodiment of the display 7012 of the interfaceunit where the combination of displayed representations informs a userthat the interface unit is in a bypass rain/freeze mode 4506 with thesensed rainfall being above the rainfall threshold 7140 and the sensedtemperature being below the temperature threshold 7146. The interfaceunit enters the bypass rain/freeze mode through user selections. Whilein the bypass mode the override indicator 7134 is displayed incooperation with the irrigation device indicator 7128 and the waterspray indicator 7130, regardless of whether a rain event and/or freezecondition are detected, and conveys that the interface unit willcontinue to allow the irrigation controller 30 to irrigate during fairweather, rain, or when a low temperature condition (e.g., a freezecondition) is determined during the bypass rain/freeze mode.

In the example of FIG. 78, the displayed rainfall indicator 7138 showsthat the rainfall exceeds the rainfall threshold 7140. In response tothe sensed rainfall exceeding the rainfall threshold 7140 the rain tripindicator 7142 is displayed. By displaying the rain trip indicator 7142,the interface unit conveys that a rain event is occurring. The examplein FIG. 78 further shows that the temperature indicator 7144 identifiesthat the sensed temperature is below the temperature threshold 7146. Inresponse, the interface unit displays the temperature trip indicator7148 to indicate to a user that a freeze condition has occurred.

When the interface unit is in the bypass rain/freeze mode 4506, however,the interface unit does not interrupt the irrigation schedule of theirrigation controller 30, even though the interface unit may determinethat one or both of a rain event and freeze condition has occurred.Further, the interrupt indicator 7132 is not displayed and the sprayedwater indicator 7130 is displayed. Thus, this displayed combination ofpictorial representations conveys to the user that even though a rainevent is occurring and/or a freeze condition is occurring irrigation isnot going to be interrupted.

In some implementations, the interface unit terminates the bypassrain/freeze mode and no longer displays the override indicator 7134, andin some instances returns to normal irrigation mode 4502, after a givenperiod of time. The given period of time can be predefined, selected bya user, defined by a user or otherwise identified. For example, theinterface unit may be kept in the bypass rain/freeze mode 4506 for apredefined 72 hours in response to a user activating the bypass.Additionally or alternatively, the user may manually return theinterface unit to normal irrigation mode 4502.

Some embodiments similarly provide a bypass rain mode 4504 that allowsirrigation even though a rain event is detected. In the bypass rain modeand during a rain event the display 7012 displays the override indicator7134 in cooperation with the irrigation device indicator 7128 and thewater spray indicator 7130 even when a rain event is detected and whilethe rain trip indicator 7142 is displayed, which conveys to the userthat the interface unit is in the bypass rain mode. During the bypassrain mode 4504, the interface unit does not interrupt the irrigationschedule and allows the irrigation controller to irrigate during fairweather, when it is raining and/or when the sensed moisture exceeds therainfall threshold 7140. While in the bypass rain mode 4504, however,the interface unit will continue to interrupt irrigation when a lowtemperature condition (e.g., a “freeze” condition) is sensed, where thelow temperature condition occurs when the sensed temperature falls belowthe temperature threshold 7146. The interface unit terminates the bypassrain mode and no longer displays the override indicator 7134, and insome instances returns to normal irrigation mode 4502, after a givenperiod of time, which can be predefined, selected by a user, defined bya user or otherwise identified. For example, the interface unit may bekept in the bypass rain/freeze mode 4506 for a predefined 72 hours inresponse to a user activating the bypass. Additionally or alternatively,the interface unit may exit the bypass rain mode when the user manuallyreturns the interface unit to normal irrigation mode 4502, or other suchconditions.

In the event that the interface unit determined a freeze conditionexisted while in the bypass rain mode 4504, the interface unit wouldproceed to the halt irrigation mode 4508 and interrupt the irrigationcontroller 30. The interface unit would further display on the display7012 the temperature trip indicator 7148 and the interrupt indicator7132 while not displaying the water spray indicator 7130, similar toFIG. 76, conveying that the interface unit is in halt irrigation mode4508 and interrupting irrigation.

FIG. 79 illustrates an embodiment of the display 7012 of the interfaceunit with the combination of displayed representations conveying thatthe interface unit is in a user activated or override halt irrigationmode 4508 (also referred to as an interrupt irrigation mode). When theinterface unit is in the halt irrigation mode 4508, the interface unitdisplays the representations of an irrigation device indicator 7128without the sprayed water indicator 7130, the interrupt indicator 7132and, in some instances, the override indicator 7134. Again, theinterrupt indicator 7132 indicates that irrigation from the irrigationcontroller is to be interrupted, hence the absence of the sprayed waterindicator 7130. The override indicator 7134 further conveys to a userthat the interrupt is user induced. Additionally, in some embodiments,the override indicator 7134 identifies an amount of time scheduled forthe interrupt and/or a remaining amount of time for the interrupt.

During the halt irrigation mode 4508, the interface unit interruptsirrigation from the irrigation controller 30. When the halt irrigationmode 4508 is triggered by a user, irrigation is interrupted regardlessof the sensed weather conditions. The user may manually place theinterface unit into the halt irrigation mode 4508 by selecting the mode(e.g., using the right arrow button 7004, the left arrow button 7006,the plus button 7008 and/or the minus button 7010). Again, the interfaceunit may enter into the halt irrigation mode 4508 from either the normalirrigation mode 4502 or the bypass modes, but in these instances thepictorial representations displayed are typically different (e.g., seeFIGS. 75-77, where the override indicator 7134 is not shown). Theinterface unit returns to the normal irrigation mode 4502 when eitherthe user manually returns the interface unit to the normal irrigationmode 4502, or automatically after a given time span. In someembodiments, the given time span is roughly three days or seventy-twohours.

In the example of FIG. 79, the display 7012 identifies through thedisplay of the select representations that the interface unit is in auser induced halt irrigation mode while the sensed rainfall as shown inthe rainfall indicator 7138 is below the rainfall threshold 7140 and thesensed temperature as shown in the temperature indicator 7144 is abovethe temperature threshold 7146, corresponding to fair weatherconditions. No bars are displayed within the rainfall indicator 7138,indicating the sensor unit has not sensed any rainfall or moisture (orthe sensed moisture is less than a threshold amount of moisture). Forthis example, since there is no sensed rainfall, the sensed rainfallfalls below the rainfall threshold 7140, such that the rain tripindicator 7142 is not displayed. Similarly, the temperature indicator7144 depicts that the sensed temperature is above the temperaturethreshold 7146, and as such the temperature trip indicator 7148 is notdisplayed. Again, the user induced halt irrigation mode allows the userto manually override the irrigation controller 30, for example, becauseof an event such as an outdoor gathering.

The above embodiments demonstrate that the interface unit provides userswith information through easily recognizable and intuitive visualpictorial, graphical or other such representations or icons. Theserepresentations make it easier for users to understand what is going onwith irrigation control as well as the conditions defining at least partof the control over the irrigation. Further, the graphical userinterface typically does not display numerical values at least withrespect to the rainfall indicator 7138, the rainfall threshold 7140, thetemperature indicator 7144 and/or the temperature threshold 7146.

It is noted, as described above, that not all of the representations arerequired, and in some embodiments one or more of the representations maynot be included and/or displayed, and/or one or more representationstemporarily may not be displayed. For example, some embodiments may notinclude or display a temperature indicator 7144 and temperaturethreshold 7146, and thus would not display or include a temperature tripindicator 7148. This may result when the interface unit is notconfigured to take into consideration temperature information. In otherembodiments, a temperature indicator 7144, temperature threshold 7146and temperature trip indicator 7148 may not be displayed through thedisplay 7012 when each of the one or more sensor units 12 incommunication with the interface unit do not include a temperaturesensor, and/or the interface unit does not otherwise receive temperatureinformation. Similarly, in some implementations, the display 7012 maynot display the rainfall indicator 7138, rainfall threshold 7140 andrain trip indicator 7142, such as when the interface unit is notcooperated with a sensor unit that can supply sensed moisture and/orrainfall information.

Additionally or alternatively, one or more of the representations thatmight typically be displayed in a certain mode temporarily may not bedisplayed. For example, one or more representations may not be displayeduntil a user interacts with the interface unit (e.g., by selecting oneor more buttons, a touch screen or such other interaction). As aspecific example, the battery remaining indicator 7118, signal strengthindicator 7120, sensor unit indicator 7126 and/or pairing statusindicator 7127 may not be displayed after a threshold amount of timeafter a most recent user interaction and be redisplayed upon subsequentuser interaction with the interface unit. As another example, thebattery remaining indicator 7118, signal strength indicator 7120, sensorunit indicator 7126 and/or pairing status indicator 7127 may not bedisplayed unless the user requests one or more of these representationsbe displayed through the selection of one or more buttons, and/or shoulda battery life fall below a threshold and/or a signal strength fallbelow a threshold. Similarly, in some instances, one or both therainfall indicator 7138 and the temperature indicator 7144 may not bedisplayed (e.g., when there is not a rain event or a low temperatureevent detected). For example, rainfall indicator 7138 and thetemperature indicator 7144 may not be displayed until and in response todetecting a rain event or a low temperature event, and/or detecting userinteraction with the interface unit.

Further, some embodiments are configured to allow a user to define andstore one or more user settings as at least part of a restore parametersetting or contractor setting. For example, a user upon setting up theinterface unit with the desired thresholds (e.g., user set rainfallthreshold and/or user set temperature threshold), the interface unit canbe activated to store these parameters as the restore parametersettings. With the parameters stored as the restore parameter settings,the user can later restore the interface unit to these restore parametersettings, such as after the user changed the settings for a period oftime (e.g., change the rainfall threshold as a result of a larger thanexpected amount of rainfall over a period of time) and/or other reasons.For example, the user can depress a specific combination of buttons onthe user interface, such as simultaneously depressing the right arrowbutton 7004 and the plus button 7008 and holding these buttons for apreset period of time (e.g., 5 seconds), to cause the current parameterand/or threshold settings to be saved as the restore parameter settings.

Once saved, the restore parameter settings can be restored at a latertime and in place of current parameters or thresholds that are differentthan those stored as the restore parameter settings. For example, torestore the restore parameter settings the user could depress a specificsequence of one or more of the buttons, such as simultaneouslydepressing both the plus button 7008 and minus button 7010 for apredefined period of time (e.g., 5 seconds). In some instances, factorysettings or other default settings can additionally or alternatively bedefined and/or used to rest the interface unit.

FIG. 80A depicts a perspective view of an interface unit 14 inaccordance with some embodiments. The interface unit 14 comprises ahousing 8012 that houses the one or more microprocessors and wirelesscommunication system. In some instances, the housing 8012 includes a lidor cover 8014. For example, the lid 8014 can be cooperated with the bodyof the housing through a hinge or other pivot. A display 8016 isincluded that displays the pictorial representations that provide theuser with information and/or status of operation. One or more user inputdevices or buttons 8020 are included that allow the user to interactwith the interface unit. Further, one or more mountings 8022 can beincluded that allow the interface unit 14 to be mounted on a wall, on aside of an irrigation controller or other such mounting, such as throughone or more screws, nuts and bolts, or the like.

FIG. 80B depicts another perspective view of the interface unit 14 ofFIG. 80A. The display 8016 cooperated with the housing 8012 is showndisplaying the graphical user interface that includes the one or morepictorial representations (e.g., the rainfall indicator 7138, therainfall threshold 7140, the temperature indicator 7144, the temperaturethreshold 7146, and other pictorial representations when relevant, suchas but not limited to the battery remaining indicator 7118, the signalstrength indicator 7120, the irrigation device indicator 7128, thesprayed water indicator 7130, the rain trip indicator 7142, thetemperature trip indicator 7148 and the like). Also illustrated is acommunication link or wiring 8030. The communication link can cooperatewith a separate switch or irrigation controller to interrupt irrigation.

Referring to FIGS. 80A-B, as described above, in many embodiments thegraphical user interface does not display numeric values, at least withrespect to the amount of accumulated rainfall, the rainfall indicator7138, the rainfall threshold 7140, the sensed temperature, thetemperature indicator 7144 and the temperature threshold 7146. Instead,the graphical user interface provides a graphical, pictorialrepresentation that is readily understandable and easily visible. Insome instances, some embodiments include printing, an insert or otherinformation provided relative to the housing 8012 and/or lid 8014.

FIG. 81 depicts a simplified representation of an insert 8032, accordingto some embodiments, that can be cooperated with an interface unit, suchas the interface unit of FIGS. 80A-B. Referring to FIGS. 80A-B and 81,for example, some embodiments include an insert 8032. The insert 8032,printing or the like can provide a user with information and/orinstructions regarding setting and adjusting parameters and/orthresholds 8110, setting the restore parameter setting or contractorsetting 8112, setting threshold parameters 8114, 8116, explanations ofthe pictorial representations 8120, and/or other information. Further,in some instances, the insert 8032 can provide numerical valuescorresponding to the different threshold settings and/or graphicaldepictions. For example, the insert 8032 can include one or more tables,listings or the like that identify the temperatures that correspond tothe predefined number of settings for the temperature threshold 7146(e.g., 41° F. (5° C.), 37° F. (3° C.), and 33° F. (0.5° C.)), theamounts of rainfall that correspond to the predefined number of settingsfor the rainfall threshold 7140 (e.g., between ⅛ inches (˜33 mm) to ½inches (˜13 mm)), and/or other such numerical information.

FIG. 82 depicts a simplified flow diagram of a process 8210 ofcontrolling irrigation in accordance with some embodiments. In step8212, a user set and adjustable rainfall threshold is received.Typically, the user set rainfall threshold is received through the userinterface integrated with an interface unit or device 14, where theinterface device is configured to use the rainfall threshold indetermining whether to cause an interruption of one or more wateringschedules executed by a separate irrigation controller.

In step 8214, sensed rainfall information is received at the interfacedevice and from a remote sensor unit 12. In some embodiments, the remotesensor unit 12 is configured to periodically communicate the senseddata. In other instances, the sensor unit is configured to communicatethe sensed data when the sensed amount of rainfall or change intemperature varies by a predefined amount. As described above, in someinstances, the rainfall indicator 7138 displays an accumulated amount ofrainfall. Accordingly, the sensor can include an accumulation sensorthat measures an accumulated amount of rainfall and transmits dataidentifying the accumulated amount to the interface device. In step8216, the interface device displays multiple pictorial representationscorresponding to the sensed rainfall information and the user set andadjustable rainfall threshold such that a state of interruptingirrigation based at least on a relationship between the sensed rainfallinformation and the user set and adjustable rainfall threshold isconveyed.

FIG. 83 depicts a simplified flow diagram of a process 8310 of settingparameters for use in controlling irrigation in accordance with someembodiments. In step 8312, signaling is received, through a plurality ofuser input devices of a user interface coupled with a controller andintegrated with a housing of the interface unit 14, designating a userset and adjustable rainfall threshold parameter and locally storing thethreshold at the interface unit. In step 8314, the controller causes oneor more pictorial representations to be displayed on a user display. Theplurality of pictorial representations are displayed in combination toconvey to the user the sensed rainfall accumulation amount, the user setrainfall threshold parameter and whether irrigation is beinginterrupted.

In step 8316, it is determined, by the one or more controllers, whetheran interruption of one or more watering schedules executed by theirrigation controller, which is separate from the interface unit, shouldoccur. When it is determined that irrigation is not to be interruptedthe process returns to step 8314 to continue to display the relevantpictorial representations. It is noted that in some instances thedisplay may enter a sleep mode where none or less than all of thepictorial representations are not displayed. This sleep mode maytemporarily display one or more of the pictorial representations (e.g.,periodically). In other instances, a trigger may awaken the system outof the sleep mode to again display the pictorial representations.

Alternatively, when it is determined that irrigation is to beinterrupted the process 8310 continues to step 8318 to cause signalingto be communicated instructing the interruption of irrigation. Theinterruption, in at least some implementations, is based at least on asensed rainfall accumulation amount and the user set rainfall thresholdparameter. In step 8320, a switching device coupled with the controllercauses the interruption in response to the signaling irrigation from thecontroller to interrupt.

In some embodiments, the irrigation control system is configured suchthat an irrigation controller obtains weather data and, morespecifically, rainfall data from one or more remote weather data serversinstead of from a series of rainfall sensors 12 a-n installed at alocation where the irrigation controller is installed, as was the casein various embodiments described above. For instance, FIG. 89illustrates an irrigation control system 8900, where irrigationcontrollers 8930 a-n (which can all be installed in one physicallocation or in locations that are remote relative to one another) areconfigured to obtain rainfall data via a remote computing system 8960from one or more weather station servers 8970 a-n. As was described inmore detail above and will be described below, each irrigationcontroller 8930 a-n is programmed to execute one or more wateringschedules and may output activation signals (e.g., 24 volt powersignals) via one or more activation lines 8932 a-n, each coupled to oneor more valves 8995 a-n located in the location to be irrigated. As iswell known, one or more sprinkler devices, drip lines and/or otherirrigation devices may be coupled to each of the valves 8995 a-n.

The exemplary computing system 8960 illustrated in FIG. 89 is a servicecloud or remote computing infrastructure including a server 8980 and adatabase 8985. The server 8980 couples to and communicates with theirrigation controllers 8930 a-n via a network 8990. The network 8990 mayinclude a cloud-based network, a wide-area network (WAN), a local areanetwork (LAN), a personal area network (PAN), a wireless local areanetwork (WLAN), or any other wired or wireless and internet or intranetnetwork, or combinations of such networks. The network 8990 provides forone-way and/or two way communications between various electronic devicesof the irrigation control system 8900. For example, as will be describedin more detail below, the network 8990 enables the server 8980 topassively receive weather data from one or more weather station servers8970 a-n or from the database 8985 at intermittent intervals and/or byactively requesting the weather data from the weather station servers8970 a-n or from the database 8985. The network 8990 also enables theserver 8980 to send control signals to the irrigation controllers 8930a-n based on the weather data received from the weather station servers8970 a-n and/or to relay the weather data received from the weatherstation servers 8970 a-n to the irrigation controllers 8930 a-n and/orto receive status notifications from the irrigation controllers 8930a-n. In some embodiments, the network 8990 permits the irrigationcontrollers 8930 a-n to obtain the weather data directly from one ormore weather station servers 8970 a-n.

In the embodiment illustrated in FIG. 89, the computing system 8960includes a remote electronic database 8985 coupled to the server 8980.In some embodiments, the database 8985 is configured to storeinformation including but not limited to geographic locations (e.g.,addresses) where the irrigation controllers 8930 a-n are installed;weather data obtained from the weather station servers 8970 a-n inassociation with the geographic locations where the irrigationcontrollers 8930 a-n are installed; dates of interruption and resumptionof watering schedules executed by the irrigation controllers 8930 a-n;status of each of the irrigation controllers 8930 a-n, etc. The database8985 may be stored, for example, on non-volatile storage media (e.g.,hard drive, flash drive, removable optical disk, etc.) internal orexternal to the server 8980, or internal or external to computingdevices separate and distinct from the server 8980. In some aspects, thedatabase 8985 is configured to obtain weather data from the weatherstation servers 8970 a-n via the network 8990. In some aspects, thedatabase 8985 is configured to obtain the weather data via the network8990 from the server 8980, which obtains the weather data from theweather station servers 8970 a-n and/or the network 8990, and transmitsthe weather data to the database 8985.

The system 8900 of FIG. 89 according to various embodiments includesweather station servers 8970 a-n configured to transmit weather data tothe server 8960 and/or the database 8985 and/or the irrigationcontrollers 8930 a-n via the network 8990. In some embodiments, theweather station servers 8970 a-n transmit weather data indicative ofrainfall in a location where each of the irrigation controllers 8930 a-nis installed. In some aspects, the weather data transmitted by theweather station servers 8970 a-n is in the form of a binary valueindicating the presence of rain (i.e., “yes rain”) or an absence of rain(i.e., “no rain”). In other aspects, the weather station servers 8970a-n transmit weather data in the form of measured accumulated rainfallamount over a given period of time (e.g., inches of rain over 1 hour, 2hours, 4 hours, 6 hours, 8 hours, 12 hours, 24 hours, 48 hours, etc.).

In some embodiments, the weather station servers 8970 a-n are configuredto transmit weather data associated with the locations where theirrigation controllers 8930 a-n are installed at predetermined hourlyintervals (e.g., 1 hour intervals, 2 hour intervals, 4 hour intervals, 6hour intervals, 12 hour intervals, 24 hour intervals, etc.), or dailyintervals (e.g., once per day, twice per day, three times per day, onceevery other day, etc.) Generally, the exact weather data transmissionintervals can be specific to each of the irrigation controllers 8930a-n, and may be determined based on historical rainfall patternsspecific to the location where each of the irrigation controllers 8930a-n is installed, or may be based on available system resources (e.g., afunction of the power usage and signaling protocol between the server8980 and the weather station servers 8970 a-n). In some configurations,the weather station servers 8970 a-n are configured to intermittentlytransmit the weather data associated with the locations where theirrigation controllers 8930 a-n are installed automatically (i.e.,without receiving a request for same from the server 8980). In otherconfigurations, the weather station servers 8970 a-n are configured tointermittently transmit the weather data associated with each of thelocations where each of the irrigation controllers 8930 are installed inresponse to a request received over the network 8990 from the server8980.

In some embodiments, which are discussed in more detail below withreference to FIGS. 89-91, the irrigation control system 8900 isconfigured such that the server 8980 obtains weather data associatedwith the locations where the irrigation controllers 8930 a-n areinstalled from respective weather station servers 8970 a-n (eitherdirectly or via the database 8985) and transmits control signals to therespective irrigation controllers 8930 a-n via the network 8990 based onthe weather data received from the weather station servers 8970 a-n. Forexample, in some aspects, the server 8980 includes a control unit thatanalyzes the weather data, specifically, the rainfall data obtained fromthe weather station servers 8970 a-n. Based on an analysis of suchweather data, the server 8980 transmits one or more irrigation controlsignals over the network 8990 to one or more of the irrigationcontrollers 8930 a-n in order to instruct one or more of the irrigationcontrollers 8930 a-n to interrupt one of more of the watering schedulesexecuted by one or more of the irrigation controllers 8930 a-n after adetected presence of rainfall in a location where each of the irrigationcontrollers 8930 a-n is installed and/or to instruct the irrigationcontrollers 8930 a-n to interrupt one or more of the watering schedulesfor a predetermined interval of time (e.g., 24 hours, 48 hours, 72hours, etc.) after a detected stop of rainfall in the locations wherethe irrigation controllers 8930 a-n are installed. In other words, insuch embodiments, the analysis of the weather data and the determinationof whether to interrupt the watering schedules executed by theirrigation controllers 8930 a-n and/or whether to remove theinterruption of the watering schedules executed by the irrigationcontrollers 8930 a-n is made centrally by the server 8980.

Generally, the server 8980 may be a stationary or portable electronicdevice, for example, one or more desktop computers, laptop computers,tablets, mobile phones, or any other electronic devices including aprocessor-based control unit and configured for data entry and one-wayand/or two-way communication (e.g., via the network 8990) with anotherdevice of the irrigation control system 8900 (e.g., database 8985,irrigation controllers 8930 a-n, weather station servers 8970 a-n,etc.), or with any other electronic device (e.g., portable electronicdevice of a customer of a service technician). With reference to FIG.90, an exemplary server 8980 is a computer-based device and includes acontrol unit (i.e., control circuit) 9014 including a processor 9016(for example, a microprocessor or a microcontroller) electricallycoupled to at least a memory 9018 and a power supply 9020. The controlunit 9014 can comprise a fixed-purpose hard-wired platform or cancomprise a partially or wholly programmable platform, an applicationspecification integrated circuit, a field programmable gate array, andso on. These architectural options are well known and understood in theart and require no further description.

In some aspects, the control circuit 9014 of the server 8980 can beconfigured (for example, by using corresponding programming stored in amemory 9018 as will be well understood by those skilled in the art) tocarry out one or more of the steps, actions, and/or functions describedherein. In some embodiments, the memory 9018 may be integral to theprocessor-based control unit 9014 or can be physically discrete (inwhole or in part) from the control unit 9014 and is configurednon-transitorily store the computer instructions that, when executed bythe control unit 9014, can cause the control unit 9014 to behave asdescribed herein. (As used herein, this reference to “non-transitorily”will be understood to refer to a non-ephemeral state for the storedcontents (and hence excludes when the stored contents merely constitutesignals or waves) rather than volatility of the storage media itself andhence includes both non-volatile memory (such as read-only memory (ROM))as well as volatile memory (such as an erasable programmable read-onlymemory (EPROM))).

Accordingly, the memory 9018 and/or the control unit 9014 may bereferred to as a non-transitory medium or non-transitory computerreadable medium.

In the exemplary embodiment of FIG. 90, the control unit 9014 of theserver 8980 is also electrically coupled to an input/output 9022, whichis a transceiver configured to receive signals from the weather stationservers 8970 a-n (e.g., rainfall data, etc.) or from any otherelectronic device (e.g., irrigation controllers 8930 a-n, database 8985,etc.) configured for communication with the server 8980 over the network8990 (e.g., a wired or wireless connection). The input/output 9022 canalso send signals to the irrigation controllers 8930 a-n (e.g., controlsignal instructing an interruption of one or more of the wateringschedules executed by the irrigation controllers 8930 a-n), or to anyother electronic device in wired or wireless communication with theserver 8980. The input/output 9022 can be integrally built into thephysical structure of the server 8990, or may be detachably coupled tothe server 8980.

In the embodiment shown in FIG. 90, the processor-based control unit9014 of the server 8980 is electrically coupled to a user interface9024, which may include a visual display or display screen 9026 (e.g.,LED screen) and/or button input 9028 that provide the user interface9024 with the ability to permit an operator of the server 8980 tomanually control the server 8980 when desired by inputting commands viatouch-screen and/or button operation and/or voice commands to, forexample, to cause the server 8980 to transmit a signal to the irrigationcontrollers 8930 a-n to cause an interruption of one or more wateringschedules executed by the irrigation controllers 8930 a-n in response toreceipt by the server 8980 of weather data indicative of active rainfallin the location where the irrigation controllers 8930 a-n are installedand/or to remove the interruption of the watering schedules after acompletion of a predetermined interval of time (e.g., 48 hours) inresponse to receipt by the server 8980 of weather data indicative of arainfall stop in the location where the irrigation controllers 8930 a-nare installed. It will be appreciated that the performance of suchfunctions by the processor-based control unit 9014 of the server 8980 isnot dependent on a human operator, and that the control unit 9014 may beprogrammed to perform such functions without a human operator.

In some embodiments, the display screen 9026 of the server 8980 isconfigured to display various graphical interface-based menus, options,and/or alerts that may be transmitted to the server 8980 (for examplefrom one or more of the irrigation controllers 8930 a-n) in connectionwith various aspects of controlling the irrigation controllers 8930 a-nvia the system 8900. The inputs 9028 of the server 8980 may beconfigured to permit an operator to navigate through the on-screen menuson the server 8980 and make changes and/or updates to various settings,including but not limited to setting the predetermined interval of time(e.g., 24 hours, 48 hours, 72 hours, 96 hours, etc.) of the interruptionof one or more watering schedules executed by the irrigation controllers8930 a-n after the server 8980 receives weather data indicative ofrainfall stop in the location where the irrigation controllers 8930 a-nare installed. It will be appreciated that such settings can be eitherpreset by a user (e.g., operator of the cloud computing infrastructure9860) via the user interface 9024 or pre-programmed into the controlunit 9014 of the server 8980. It will be also appreciated that thedisplay screen 9026 may be configured as both a display screen and aninput 9028 (e.g., a touch-screen that permits an operator to press onthe display screen 9026 to enter text and/or execute commands.)

In some embodiments, the control circuit 9014 of the server 8980 isprogrammed to obtain weather data associated with the location whereeach of the irrigation controllers 8930 a-n is installed. In someaspects, such weather data is obtained by the server 8980 via thenetwork 8990 from the weather station servers 8970 a-n at predeterminedintervals. Such intervals may be predetermined hourly intervals (e.g., 1hour, 2 hour, 4 hour, 6 hour, 12 hour, 24 hour, etc.), or may be dailyintervals (e.g., once per day, twice per day, three times per day, onceevery other day, etc.) As mentioned above, in some embodiments, thecloud-based server 8980 passively receives weather data from one or moreweather station servers 8970 a-n via the network 8990 or from thedatabase 8985 via the network 8990 (or an electrical connection) atintermittent intervals. In some embodiments, the control circuit 9014causes the server 8980 to actively request (e.g., by transmitting asignal over the network 8990) the weather data from the weather stationservers 8970 a-n or from the database 8985. As discussed above, theexact intervals can be determined based on historical rainfall patternsspecific to the locations where the irrigation controllers 8930 a-n areinstalled, or based on system resources (e.g., a function of the powerusage and signaling protocol between the server 8980 and weather stationservers 8970 a-n).

In some embodiments, the control circuit 9014 of the cloud-based server8980 is programmed to analyze the weather data received from the weatherstation servers 8970 a-n, and to cause an interruption of one or morewatering schedules executed by the irrigation controllers 8930 a-n inresponse to a determination by the control circuit 9014 of the server8980 that the weather data obtained by the server 8980 from the weatherstation servers 8970 a-n indicates active rainfall in one or more of thelocations where the irrigation controllers 8930 a-n are installed. Insome aspects, the weather data obtained by the server 8980 and analyzedby the control unit 9014 is simple “rain” or “no rain” data and/oraccumulated rainfall data (e.g., inches of rain per time period).

For example, if the weather data obtained by the server 8980 indicatesthat rain is present in the location where one or more of the irrigationcontrollers 8930 a-n are installed, the control circuit 9014 isprogrammed to transmit, directly or via an intermediate electronicdevice (e.g., via the network 8990 and/or an intermediate computingdevice or server), a control signal to the respective one or more of theirrigation controllers 8930 a-n configured to interrupt one or more ofthe watering schedules executed by such irrigation controllers 8930 a-n.In other words, the interruption of the watering schedules executed bythe irrigation controllers 8930 a-n in such embodiments is caused by theserver 8980 based on the fact that the weather data received from theweather station servers 8970 a-n for a given time period indicates thatit has rained during the reporting time period and/or is currentlyraining in the location where one or more of the irrigation controllers8930 a-n are installed.

In some embodiments, the control unit 9014 of the server 8980 isconfigured to transmit a signal configured to cause an interruption ofone or more watering schedules executed by one or more of the irrigationcontrollers 8930 a-n based on receiving weather data from the weatherstation servers 8970 a-n indicating that rain accumulation (e.g.,inches) is above a set rainfall accumulation threshold parameter. Therainfall accumulation threshold parameter, which was discussed in moredetail above, may be defined by being preprogrammed into the controlunit 9014 of the server 8980, or may be a user-defined adjustableparameter, e.g., selected from a plurality of user selectableaccumulation threshold parameters.

In other words, the interruption of the watering schedules executed bythe irrigation controllers 8930 a-n in such embodiments is caused by theserver 8980 based on the fact that the weather data received from theweather station servers 8970 a-n indicates that the amount of rain inone or more locations where one or more of the irrigation controllers8930 a-n are installed has exceeded a predefined water accumulationthreshold. As such, in some aspects, if the weather data obtained by theserver 8980 indicates that the rainfall in the location where one ormore of the irrigation controllers 8930 a-n is installed was for a shortduration or not strong enough to achieve the predefined wateraccumulation threshold for interrupting the watering schedules executedby such irrigation controllers 8930 a-n, the control unit 9014 of theserver 8980 will not send an irrigation-interrupting control signal tosuch irrigation controllers 8930 a-n and such irrigation controllers8930 a-n will continue to operate in normal irrigation mode.

In some embodiments, the above-described signal, when received by theirrigation controllers 8930 a-n from the server 8980, causes theirrigation controllers 8930 a-n to interrupt one or more of the wateringschedules executed by the irrigation controllers 8930 a-n such thatirrigation is suspended in response to rainfall detection in therespective locations where the irrigation controllers 8930 a-n areinstalled. As a result, the watering schedules executed by theirrigation controllers 8930 a-n continue to be interrupted following thepredetermined interval of time after rainfall has stopped. In someaspects, the control circuit 9014 is configured to remove theinterruption of the one or more watering schedules by the irrigationcontrollers 8930 a-n after a completion of a predetermined interval oftime (e.g., 24 hours, 48 hours, 72 hours, 96 hours, etc.) following thereceipt by the server 8980 from the weather station servers 8970 a-n ofweather data indicative of a rainfall stop in the respective locationswhere the irrigation controllers 8930 a-n are installed. In other words,after the predetermined interval of time of the interruption (e.g., 48hours) elapses, the control unit 9014 of the server 8980 removes theinterruption of the one or more watering schedules executed by one ormore of the irrigation controllers 8930 a-n (e.g., by transmitting asignal configured to activate the respective irrigation controllers 8930a-n), thereby permitting such irrigation controllers 8930 a-n to executeone or more watering schedules by activating one or more valves 8995 a-nin normal irrigation mode.

As discussed above, the interval of time for which the control unit 9014of the server 8980 is configured to maintain an interruption of one ormore watering schedules executed by the irrigation controllers 8930 a-ncan be 24 hours, 48 hours, 72 hours (or longer), and may bepreprogrammed into the control unit of the server 8980, or may be preset(and adjustable) by a user of the server 8980. As discussed above, whileexemplary intervals of time are provided, the interval of time may beany length of time that is suitable to the needs of the overallirrigation control system 8900 and balances the use of water forirrigation and conserving water resources. For instance, in certainembodiments, the control unit 9014 of the server 8980 is programmed tomaintain an interruption of one or more watering schedules executed bythe irrigation controllers 8930 a-n for a number of hours (or number ofdays) dependent on, for example, a number of days or hours ofconsecutive rain or a number of inches or rain accumulated from thestart of rainfall to the end of rainfall in the locations where theirrigation controllers 8930 a-n are installed.

In other words, if the control unit 9014 of the server 8980 determinesthat the weather data obtained by the server 8980 from the weatherstation servers 8970 a-n indicates that there were 5 consecutive days ofrain in the location where one or more of the irrigation controllers8930 a-n is/are installed, the control unit 9014 may be programmed tocause an interruption (e.g., 48 hours, 72 hours, 96 hours, 120 hours,etc.) that is for a longer period of time than an interruption that thecontrol unit 9014 would cause if the weather data obtained by the server8980 from the weather station servers 8970 a-n were to indicate thatthere were 4 consecutive days of rain in the location where suchirrigation controller(s) 8930 a-n is/are installed. Similarly, if theweather data obtained by the server 8980 from the weather stationservers 8970 a-n indicates that 10 inches of rainfall accumulated duringa period of rainfall in the location where one or more of the irrigationcontrollers 8930 a-n is/are installed, the control unit 9014 may beprogrammed to cause an interruption (e.g., 48 hours, 72 hours, 96 hours,120 hours, etc.) that is for a longer period of time than aninterruption that the control unit 9014 would cause if the weather dataobtained by the server 8980 from the weather station servers 8970 a-nwere to indicate that 5 inches of rainfall accumulated during a periodof rainfall in the location where such irrigation controller(s) 8930is/are installed. As discussed above, while exemplary intervals of timeare provided, the interval of time may be any length of time that issuitable to the needs of the overall watering system and balances theuse of water for irrigation and conserving water resources.

As a result of the above-described interruption of the irrigationschedules executed by the irrigation controllers 8930 a-n by the controlunit 9014 of the server 8980 for a predetermined interval of timefollowing a detected end of rainfall in the respective locations wherethe irrigation controllers 8930 a-n are installed, the wateringschedules that are normally executed by the irrigation controllers 8930a-n are not resumed immediately after the server 8980 receives weatherdata indicating that the rain has stopped in the respective locationswhere the irrigation controllers 8930 a-n are installed, therebyadvantageously providing an interruption of irrigation designed to belong enough for the respective locations where the irrigationcontrollers 8930 a-n are installed to ensure that the benefit of naturalwatering to rainfall is provided without over or unnecessarily watering,and not be so long that the plant life being watering is endangered dueto lack of water.

In some aspects, the control unit 9014 of the server 8980 is configuredsuch that, when the server 8980 receives signaling from the weatherstation servers 8970 a-n indicative of a rainfall stop (e.g., “no rain,”“0.0 inches of rain,” etc.) in locations where one or more of theirrigation controllers 8930 a-n are installed, the control unit 9014 ofthe server 8980 initiates a timer configured to count down a remainderof time left on the predetermined interval of time of the interruptionof the one or more watering schedules executed by the respectiveirrigation controllers 8930 a-n. For example, if the control unit 9014is configured such that the predetermined interval of time of theinterruption of irrigation after receipt by the server 8980 of weatherdata indicative of a rainfall stop is 48 hours, after the control unit9014 obtains weather data from one or more of the weather stationservers 8970 a-n indicative of a rainfall stop in the respectivelocations where the irrigation controllers 8930 a-n are installed, thecontrol unit 9014 initiates a timer configured to count down 48 hoursfrom a point of time when such end of rainfall-indicating weather datais obtained. During active rainfall and during this 48 hour windowfollowing the stop of rainfall, one or more of the watering schedulesexecuted by the irrigation controllers 8930 a-n will be interrupted bythe control unit 9014 of the server 8980.

In some embodiments, while the timer activated by the control unit 9014of the server 8980 counts down the remainder of time left on thepredetermined interval of time of the interruption of the wateringschedules executed by the irrigation controllers 8930 a-n after receiptof weather data indicative of a stop of rainfall in the respectivelocations where the irrigation controllers 8930 a-n are installed, thecontrol unit 9014 of the server 8980 is configured to continue obtainingthe weather data from the weather station servers 8970 a-n at theintermittent intervals (e.g., hourly intervals or daily intervals)discussed above. In some embodiments, the control unit 9014 of theserver 8980 is configured to determine that the weather data signalsobtained from the weather station servers 8970 a-n at one of theaforementioned intermittent intervals during the timer-based countdownindicates no rainfall in the respective locations of the irrigationcontrollers 8930 a-n. In one aspect, based on such a determination, thecontrol unit 9014 of the server 8980 permits the timer to continue thecountdown of the remainder of time left on the interval of time (e.g.,48 hours) of the interruption of irrigation.

In other words, in some aspects, so long as the control unit 9014receives weather data from the weather station servers 8970 a-nindicative of no rainfall in the respective locations where theirrigation controllers 8930 a-n are installed, the control unit 9014 ofthe server 8980 permits the timer for the respective irrigationcontrollers 8930 a-n to continuously count down to zero the remainder oftime left on the interval of time of the interruption of irrigation. Insome embodiments, after the timers associated with respective ones ofthe irrigation controllers 8930 a-n continuously count down to zero theremainder of time left on the interval of time of the interruption, thecontrol unit 9014 of the server 8980 removes the interruption of the oneor more watering schedules executed by such irrigation controllers 8930a-n (e.g., by transmitting a signal configured to activate suchirrigation controllers 8930 a-n), thereby permitting the respectiveirrigation controllers 8930 a-n to execute one or more wateringschedules in normal irrigation mode.

In some embodiments, the control unit 9014 of the server 8980 isconfigured to determine that the weather data obtained from the weatherstation servers 8970 a-n at one of the aforementioned intermittentintervals (during which the timer counts down the predetermined intervalof time of the interruption) indicates a presence of rain. In responseto this determination, in some aspects, the control unit 9014 of theserver 8980 resets the aforementioned timer to restart the countdown ofthe remainder of time left on the predetermined interval of time of theinterruption of irrigation. In other words, in some aspects, when,during a countdown of the predetermined interval of time of theinterruption of irrigation, the server 8980 receives weather data fromthe weather data stations 8970 a-n indicative of active rainfall inrespective locations where the irrigation controllers 8930 a-n areinstalled, the control unit 9014 of the server 8980 restarts the timerassociated with respective ones of the irrigation controllers 8930 a-nto the beginning of the countdown. Then, if the timers associated withrespective ones of the irrigation controllers 8930 a-n count down tozero the remainder of time left on the predetermined interval of time ofthe interruption of irrigation with no intervening rainfall in therespective locations where such irrigation controllers 8930 a-n areinstalled (which would again reset the respective timers), theinterruption of the one or more watering schedules executed by therespective ones of the irrigation controllers 8930 a-n is removed by thecontrol unit 9014 of the server 8980 (e.g., by way of sending anappropriate signal to the irrigation controller 8930), and theirrigation controller 8930 is permitted to execute the one or morewatering schedules in normal irrigation mode.

FIG. 91 depicts a simplified flow diagram of an exemplary process 9100of controlling irrigation based on rainfall in accordance with someembodiments. In step 9112, one or more irrigation controllers 8930 a-nconfigured to execute one or more watering schedules are provided. Instep 9114 of the process 9100, a server 8980 remote to respectivelocations where the irrigation controllers 8930 a-n are installed isprovided. As described above, the server 8980 is configured forcommunication with the irrigation controllers 8930 a-n over a network8990 and includes a control unit 9014. Step 9116 of the process 9100illustrated in FIG. 91 includes obtaining, via the control unit 9014 ofthe server 8930, weather data associated with the respective locationswhere the irrigation controllers 8930 a-n are installed. In step 9116,the control unit 9014 of the server 8980 causes an interruption of oneor more watering schedules executed by the irrigation controllers 8930a-n in response to receipt by the server 8980 of weather data indicativeof active rainfall in the respective location where such irrigationcontrollers 8930 a-n are installed. Step 9120 of the exemplary method9100 of FIG. 91 includes removing, via the control unit 9014 of theserver 8980, the interruption after a completion of a predeterminedinterval of time (e.g., 48 hours etc.) in response to receipt by thecloud-based server 8980 of weather data (e.g., from the weather stationservers 8970 a-n or database 8985) indicative of a rainfall stop in therespective locations where the irrigation controllers 8930 a-n areinstalled.

In some embodiments, which will be discussed with reference to FIGS. 89,92, and 93, the irrigation control system 8900 is configured such thatthe server 8980 obtains weather data associated with locations where theirrigation controllers 8930 a-n are installed from weather stationservers 8970 a-n (either directly or via the database 8985) and relaysthe obtained weather data to the respective irrigation controllers 8930a-n via the network 8990 (which can be wired or wireless). In someaspects, after the server 8980 relays the rainfall data obtained fromthe weather station servers 8970 a-n in signals over the network 8990 tothe irrigation controllers 8930 a-n, the irrigation controllers 8930 a-nanalyze their respective rainfall data obtained from the weather stationservers 8970 a-n via the server 8980. Based on this analysis by theirrigation controllers 8930 a-n, the irrigation controllers 8930 a-ndetermine to interrupt one of more of their respective wateringschedules after a detected active rainfall in their respectiveinstallation locations and/or to interrupt the one or more of thewatering schedules for a predetermined interval (e.g., 24 hours, 48hours, 72 hours, etc.) of time after a detected stop of rainfall intheire respective installation locations. In other words, in suchembodiments, the analysis of the weather data and the determination ofwhether to interrupt the watering schedules executed by the irrigationcontrollers 8930 a-n and/or whether to remove the interruption of thewatering schedules executed by the irrigation controllers 8930 a-n ismade by the irrigation controllers 8930 a-n themselves, not by theremote server 89800.

FIG. 92 depicts a functional diagram of the components of an irrigationcontroller 8930 representative of the irrigation controllers 8930 a-n,which is configured to analyze weather data and determine whether tointerrupt the watering schedules executed by the irrigation controller8930 and/or whether to remove the interruption of the watering schedulesexecuted by the irrigation controller 8930 according to some embodimentsof the system 8900. With reference to FIG. 92, the exemplary irrigationcontroller 8930 includes a control unit (i.e., control circuit) 9214including a processor 9216 (for example, a microprocessor or amicrocontroller) electrically coupled to at least a memory 9218 and apower supply 9220.

The control unit 9214 of the exemplary irrigation controller 8930 cancomprise a fixed-purpose hard-wired platform or can comprise a partiallyor wholly programmable platform, an application specification integratedcircuit, a field programmable gate array, and so on. These architecturaloptions are well known and understood in the art and require no furtherdescription. It will be appreciated that the components of the exemplaryirrigation controller 8930 illustrated in FIG. 92 are shown by way ofexample only, and that one or more of the illustrated components areoptional features, and that the irrigation controller 8930 mayadditionally include or be coupled to other components. In addition,while some of the components within the exemplary irrigation controller8930 are depicted in FIG. 92 as separate components, it will beappreciated that such components may be combined together as onecomponent, or any combination thereof.

In some aspects, the control circuit 9214 of the irrigation controller8930 can be configured (for example, by using corresponding programmingstored in a memory 9218 as will be well understood by those skilled inthe art) to carry out one or more of the steps, actions, and/orfunctions described herein. In some embodiments, the memory 9218 may beintegral to the processor-based control unit 9214 or can be physicallydiscrete (in whole or in part) from the control unit 9214 and isconfigured non-transitorily store the computer instructions that, whenexecuted by the control unit 9214, can cause the control unit 9214 tobehave as described herein. (As used herein, this reference to“non-transitorily” will be understood to refer to a non-ephemeral statefor the stored contents (and hence excludes when the stored contentsmerely constitute signals or waves) rather than volatility of thestorage media itself and hence includes both non-volatile memory (suchas read-only memory (ROM)) as well as volatile memory (such as anerasable programmable read-only memory (EPROM))). Accordingly, thememory 9218 and/or the control unit 9214 may be referred to as anon-transitory medium or non-transitory computer readable medium.

In the exemplary embodiment of FIG. 92, the control unit 9214 of theirrigation controller 8930 is also electrically coupled to aninput/output 9222, which is a transceiver configured to receive signalsfrom the weather station servers 8970 a-n (e.g., rainfall data, etc.) orfrom any other electronic device (e.g., server 8980, database 8985,etc.) configured for communication with the irrigation controller 8930over the network 8990. The input/output 9222 can also send signals tothe server 8930 and/or database 8985 (e.g., signal indicating start ofan interruption of one or more of the watering schedules executed by theirrigation controller 8930), or to any other electronic device in wiredor wireless communication with the irrigation controller 8930. Theinput/output 9222 can be integrally built into the physical structure ofthe irrigation controller 8930, or may be detachably coupled to theirrigation controller 8930. As mentioned above, the irrigationcontrollers 8930 a-n are coupled to their respective activation lines8932 a-n and may output activation signals (e.g., via the input/output9222 or via another control switch) to respective ones of the activationlines 8932 a-n, each coupled to a valve 8995 a-n located in the locationto be irrigated.

In the embodiment shown in FIG. 92, the processor-based control unit9214 of the irrigation controller 8930 is electrically coupled to a userinterface 9224, which may include a visual display or display screen9226 (e.g., LED screen) and/or button input 9228 that provide the userinterface 9224 with the ability to permit an operator of the irrigationcontroller 8930 to manually control the irrigation controller 8930 whendesired by inputting commands via touch-screen and/or button operationand/or voice commands. Such commands can enable the operator, forexample, to cause the irrigation controller 8930 to cause aninterruption of one or more watering schedules executed by theirrigation controller 8930 in response to receipt of weather dataindicative of active rainfall in the location where the irrigationcontroller 8930 is installed and/or to remove the interruption of thewatering schedules after a completion of a predetermined interval oftime (e.g., 48 hours) in response to receipt of weather data indicativeof a rainfall stop in the location where the irrigation controller 8930is installed. It will be appreciated that the performance of suchfunctions by the processor-based control unit 9214 of the irrigationcontroller 8930 is not dependent on a human operator, and that thecontrol unit 9214 may be programmed to perform such functions without ahuman operator. In some aspects, the user input data received (by touchbutton-based entry or wireless device-based entry) via the userinterface 9224 (e.g., irrigation settings, rain delay irrigation hold,etc.) is also sent to the control unit 9214.

In some aspects, the display screen 9226 of the irrigation controller8930 is configured to display various graphical interface-based menus,options, and/or alerts that may be transmitted to the irrigationcontroller 8930 (for example from the server 8980 or database 8985) inconnection with various aspects of controlling the irrigation controller8930. The inputs 9228 of the irrigation controller 8930 may beconfigured to permit an on-site or remotely connected operator tonavigate through the on-screen menus on the irrigation controller 8930and make changes and/or updates to various settings, including but notlimited to setting the predetermined interval of time (e.g., 24 hours,48 hours, 72 hours, 96 hours, etc.) of the interruption of one or morewatering schedules executed by the irrigation controller 8930 after theirrigation controller 8930 receives weather data indicative of rainfallstop in the location where the irrigation controller 8930 is installed.It will be appreciated that such settings can be either preset by theoperator via the user interface 9224 or pre-programmed into the controlunit 9214 of the irrigation controller 8930. It will be also appreciatedthat the display screen 9226 may be configured as both a display screenand an input 9228 (e.g., a touch-screen that permits an operator topress on the display screen 9226 to enter text and/or execute commands.)

In some embodiments, the control circuit 9214 of the irrigationcontroller 8930 is programmed to obtain weather data associated with thelocation where the irrigation controller 8930 is installed. In someaspects, such weather data is obtained by the irrigation controller 8930via the communication links 8975 a-n and/or network 8990 from theweather station servers 8970 a-n at predetermined intervals. Asdescribed above, such intervals may be predetermined hourly intervals(e.g., 1 hour, 2 hour, 4 hour, 6 hour, 12 hour, 24 hour, etc.), or maybe daily intervals (e.g., once per day, twice per day, three times perday, once every other day, etc.)

In some embodiments, the exemplary irrigation controller 8930 of FIG. 92passively receives weather data from one or more weather station servers8970 a-n via the network 8990 or from the database 8985 via the network8990 or an electrical connection at intermittent intervals. In someembodiments, the control circuit 9214 causes the irrigation controller8930 to actively request (e.g., by transmitting a signal over thenetwork 8990) the weather data from one or more of the weather stationservers 8970 a-n or from the database 8985. As discussed above, theexact intervals can be determined based on historical rainfall patternsspecific to the location where the irrigation controller 8930 isinstalled, or based on system resources (e.g., a function of the powerusage and signaling protocol between the irrigation controller 8930 andthe weather station servers 8970 a-n).

In various embodiments, the control circuit 9214 of the exemplaryirrigation controller 8930 of FIG. 92 is programmed to analyze theweather data received from the weather station servers 8970 a-n, and tocause an interruption of one or more watering schedules executed by theirrigation controller 8930 in response to a determination by the controlcircuit 9214 of the irrigation controller 8930 that the weather dataobtained by the irrigation controller 8930 from the weather stationservers 8970 a-n indicates active rainfall in the location where theirrigation controller 8930 is installed. In some aspects, the weatherdata obtained by the irrigation controller 8930 and analyzed by thecontrol unit 9014 is simple “rain” or “no rain” data and/or accumulatedrainfall data (e.g., inches of rain per a defined time period).

For example, if the weather data obtained by the irrigation controller8930 indicates that rain is present in the location where the irrigationcontroller 8930 is installed, the control circuit 9214 is programmed togenerate and/or transmit (e.g., to a switching device 9217 (which iscoupled to activation line(s) associated with the irrigation controller8930 and/or to the input/output 9222 in communication with theactivation line(s) associated with the irrigation controller 8930) acontrol signal configured to interrupt one or more of the wateringschedules executed by the irrigation controller 8930. In some aspects,the control circuit 9214 is configured to transmit a signal and/oractivate a relay device and/or a switching device and/or another similardevice in order to disable all electrical signals transmitted along theactivation lines 8932 a-n to the valves 8995 a-n, thereby interruptingone or more watering schedules. In other words, the interruption of thewatering schedules executed by the irrigation controller 8930 in suchembodiments is caused by the control unit 9214 of the irrigationcontroller 8930 based on a determination by the control unit 9214 thatthe weather data received from the weather station servers 8970 a-n fora given time period indicates that it has rained during the reportingtime period and/or is currently raining in the location where theirrigation controller 8930 is installed.

In some embodiments, the control unit 9214 of the irrigation controller8930 is configured to generate and/or transmit a signal configured tocause an interruption of one or more watering schedules executed by theirrigation controller 8930 based on receiving weather data from theweather station servers 8970 a-n indicating that rain accumulation(e.g., inches) is above a set rainfall accumulation threshold parameter.The rainfall accumulation threshold parameter, which was discussed inmore detail above, may be defined by being preprogrammed into thecontrol unit 9214 of the irrigation controller 8930, or may be auser-defined adjustable parameter, e.g., selected from a plurality ofuser selectable accumulation threshold parameters.

In other words, the interruption of the watering schedules executed bythe irrigation controller 8930 in such embodiments is caused by thecontrol unit 9214 of the irrigation controller based on a determinationby the control unit 9214 that the weather data received from the weatherstation servers 8970 a-n indicates that the amount of rain in thelocation where the irrigation controller 8930 is installed has exceededa predefined water accumulation threshold. As such, in some aspects, ifthe weather data obtained by the irrigation controller 8930 indicatesthat the rainfall in the location where the irrigation controller 8930is installed was for a short duration or not strong enough to achievethe predefined water accumulation threshold for interrupting thewatering schedules executed by the irrigation controller 8930, thecontrol unit 9214 of the irrigation controller 8930 will not generate ortransmit an irrigation-interrupting control signal 8930, and theirrigation controller 8930 will continue to operate in normal irrigationmode.

In some embodiments, the above-described signal, when generated by thecontrol unit 9214 of the irrigation controller 8930, causes theirrigation controller 8930 to interrupt one or more of the wateringschedules executed by the irrigation controller 8930 such thatirrigation is suspended in response to rainfall detection in thelocation where the irrigation controller 8930 is installed. As a result,the watering schedules executed by the irrigation controller 8930continue to be interrupted following the predetermined interval of timeafter rainfall has stopped. In some aspects, the control circuit 9214 isconfigured to remove the interruption of the one or more wateringschedules by the irrigation controller 8930 after a completion of apredetermined interval of time (e.g., 24 hours, 48 hours, 72 hours, 96hours, etc.) following the receipt by the irrigation controller 8930from the weather station servers 8970 a-n of weather data indicative ofa rainfall stop in the location where the irrigation controller 8930 isinstalled. In other words, after the predetermined interval of time ofthe interruption (e.g., 48 hours) elapses, the control unit 9214 of theirrigation controller 8930 removes the interruption of the one or morewatering schedules executed by the irrigation controller 8930 (e.g., bygenerating a signal configured to activate the irrigation controller8930), thereby permitting the irrigation controller 8930 to execute thewatering schedules by activating one or more valves 8995 in normalirrigation mode.

As discussed above, the interval of time for which the control unit 9214of the irrigation controller 8930 is configured to maintain aninterruption of one or more watering schedules executed by theirrigation controller 8930 can be 24 hours, 48 hours, 72 hours (orlonger), and may be preprogrammed into the control unit 9214 of theirrigation controller 8930, or may be preset (and adjustable) by a userof the irrigation controller 8930 (or by the manufacturer). As discussedabove, while exemplary intervals of time are provided, the interval oftime may be any length of time that is suitable to the needs of theoverall irrigation control system 8900 and balances the use of water forirrigation and conserving water resources. For instance, in certainembodiments, the control unit 9214 of the irrigation controller 8930 canbe programmed to maintain an interruption of one or more wateringschedules executed by the irrigation controller 8930 for a number ofhours (or number of days) dependent on, for example, a number of days orhours of consecutive rain or a number of inches or rain accumulated fromthe start of rainfall to the end of rainfall in the location where theirrigation controller 8930 is installed.

In other words, if the control unit 9214 determines that the weatherdata obtained by the irrigation controller 8930 from the weather stationservers 8970 a-n indicates that there were two consecutive days of rainin the location where the irrigation controller 8930 is installed, thecontrol unit 9214 may be programmed to cause an interruption (e.g., 24hours, 48 hours, 72 hours, etc.) that is for a longer period of timethan an interruption that the control unit 9214 would cause if theweather data obtained by the irrigation controller 8930 from the weatherstation servers 8970 a-n were to indicate that there was only one day ofrain in the area where the irrigation controller 8930 is installed.Similarly, if the weather data obtained by the irrigation controller8930 from the weather station servers 8970 a-n indicates that fiveinches of rainfall accumulated during a period of rainfall in the areawhere the irrigation controller 8930 is installed, the control unit 9214may be programmed to cause an interruption (e.g., 24 hours, 48 hours, 72hours, etc.) that is for a longer period of time than an interruptionthat the control unit 9214 would cause if the weather data obtained bythe irrigation controller 8930 from the weather station servers 8970 a-nwere to indicate that two inches of rainfall accumulated during a periodof rainfall in the area where the irrigation controller 8930 isinstalled. As discussed above, while exemplary intervals of time areprovided, the interval of time may be any length of time that issuitable to the needs of the overall watering system and balances theuse of water for irrigation and conserving water resources.

As a result of such interruption of the irrigation schedules executed bythe irrigation controller 8930 caused by the control unit 9214 of theirrigation controller 8930 for a predetermined interval of timefollowing a detected end of rainfall in the location where theirrigation controller 8930 is installed, the watering schedules that arenormally executed by the irrigation controller 8930 are not resumedimmediately after the irrigation controller 8930 receives weather dataindicating that the rain has stopped in the location where theirrigation controller 8930 is installed, thereby advantageouslyproviding an interruption of irrigation designed to be long enough forthe location where the irrigation controller 8930 is installed to ensurethat the benefit of natural watering to rainfall is provided withoutover or unnecessarily watering, and not be so long that the plant lifebeing watering is endangered due to lack of water.

In some aspects, the control unit 9214 of the irrigation controller 8930is configured such that, when the irrigation controller 8930 receivessignaling from the weather station servers 8970 a-n indicative of arainfall stop (e.g., “no rain,” “0.0 inches of rain,” etc.), the controlunit 9214 of the irrigation controller 8930 initiates a timer configuredto count down a remainder of time left on the predetermined interval oftime of the interruption of the one or more watering schedules executedby the irrigation controller 8930. For example, if the control unit 9214is configured such that the predetermined interval of time of theinterruption of irrigation after receipt by the irrigation controller8930 of weather data indicative of a rainfall stop is 48 hours, afterthe control unit 9214 obtains weather data from one or more of theweather station servers 8970 a-n indicative of a rainfall stop in thelocation where the irrigation controller 8930 is installed, the controlunit 9214 initiates a timer configured to count down 48 hours from apoint of time when such end of rainfall-indicating weather data isobtained. During active rainfall and during this 48 hour windowfollowing the stop of rainfall, one or more of the watering schedulesexecuted by the irrigation controller 8930 will be interrupted by thecontrol unit 9214 of the irrigation controller 8930.

In some embodiments, while the timer activated by the control unit 9214of the irrigation controller 8930 counts down the remainder of time lefton the predetermined interval of time of the interruption of thewatering schedules executed by the irrigation controller 8930 afterreceipt of weather data indicative of a stop of rainfall in the locationwhere the irrigation controller 8930 is installed, the control unit 9214of the irrigation controller 8930 is configured to continue obtainingthe weather data from the weather station servers 8970 a-n at theintermittent intervals (e.g., hourly intervals or daily intervals)discussed above. In some embodiments, the control unit 9214 of theirrigation controller 8930 is configured to determine that the weatherdata signals obtained from the weather station servers 8970 a-n at oneof the aforementioned intermittent intervals during the timer-basedcountdown indicates no rainfall. In one aspect, based on such adetermination, the control unit 9214 of the irrigation controller 8930permits the timer to continue the countdown of the remainder of timeleft on the interval of time (e.g., 48 hours) of the interruption ofirrigation.

In other words, in some aspects, so long as the control unit 9214receives weather data from the weather station servers 8970 a-nindicative of no rainfall in the location where the irrigationcontroller 8930 is installed, the control unit 9214 of the irrigationcontroller 8930 permits the timer to continuously count down to zero theremainder of time left on the interval of time of the interruption ofirrigation. In some embodiments, after the timer continuously countsdown to zero the remainder of time left on the interval of time of theinterruption, the control unit 9214 of the irrigation controller 8930removes the interruption of the one or more watering schedules executedby the irrigation controller 8930 (e.g., by transmitting a signal to theswitching device 9217 and/or input/output 9222 and/or along activationlines 9232), thereby permitting the irrigation controller 8930 toexecute one or more watering schedules in normal irrigation mode.

In some embodiments, the control unit 9214 of the exemplary irrigationcontroller 8930 of FIG. 92 is configured to determine that the weatherdata obtained from the weather station servers 8970 a-n at one of theaforementioned intermittent intervals (during which the timer countsdown the predetermined interval of time of the interruption) indicates apresence of rain. In response to this determination, in some aspects,the control unit 9214 of the irrigation controller 8930 resets theaforementioned timer to restart the countdown of the remainder of timeleft on the predetermined interval of time of the interruption ofirrigation.

In other words, in some aspects, when, during a countdown of thepredetermined interval of time of the interruption of irrigation, theirrigation controller 8930 receives weather data from the weather datastations 8970 a-n indicative of active rainfall in the location wherethe irrigation controller 8930 is installed, the control unit 9214 ofthe irrigation controller 8930 restarts the timer to the beginning ofthe countdown. Then, if the timer counts down to zero the remainder oftime left on the predetermined interval of time of the interruption ofirrigation with no intervening rainfall in the location where theirrigation controller 8930 is installed (which would again reset thetimer), the interruption of the one or more watering schedules executedby the irrigation controller 8930 is removed by the control unit 9214 ofthe irrigation controller 8930 as described above, and the irrigationcontroller 8930 is permitted to execute the watering schedules in normalirrigation mode.

FIG. 93 depicts a simplified flow diagram of a process 9300 ofcontrolling irrigation based on rainfall in accordance with someembodiments. In step 9312, an irrigation controller 8930 configured toexecute one or more watering schedules is provided. In step 9314 of theprocess 9300, a server 8980 remote to a location where the irrigationcontroller 8930 is installed is provided. As described above, the server8980 is configured for communication with the irrigation controller 8930over a network 8990. Step 9316 of the process 9300 illustrated in FIG.93 includes obtaining, via the irrigation controller 8930 and over thenetwork 8990, weather data associated with the location where theirrigation controller 8930 is installed. In step 9316, the control unit9214 of the irrigation controller 8930 causes an interruption of one ormore watering schedules executed by the irrigation controller 8930 inresponse to receipt by the irrigation controller 8930 of weather dataindicative of active rainfall in the location where the irrigationcontroller 8930 is installed. Finally, step 9320 of the exemplary method9300 of FIG. 93 includes removing, via the control unit 9214 of theirrigation controller 8930, the interruption after a completion of apredetermined interval of time (e.g., 48 hours etc.) in response toreceipt by the irrigation controller 8930 of weather data (e.g., fromthe server 8980, database 8985, or one or more weather station servers8970 a-n) indicative of a rainfall stop in the location where theirrigation controller 8930 is installed.

It will be appreciated that while in the exemplary embodiment describedabove the system 8900 was configured such that the irrigation controller8930 received the weather data from the weather station servers 8970 a-nindirectly (i.e., via the server 8980), in some embodiments, theirrigation control system may be configured such that rainfall data istransmitted from the weather station servers directly to the irrigationcontrollers (i.e., without first being transmitted to the server 8980and/or the database 8985). FIG. 94, discussed below, illustrates anexemplary embodiment of such a system, which does utilize anintermediate server to facilitate the receipt of weather data from theweather station servers by the irrigation controllers.

With reference to FIG. 94, the system 9400 is configured such that theweather station servers 9470 a-n and the irrigation controllers 9430 a-nare in communication via the network 9490 (which may be a wired orwireless network as discussed above) such that weather data (and inparticular, rainfall data) is transmitted from the weather stationservers 9470 a-n directly to the irrigation controllers 9430 a-n. Uponreceipt of their respective weather data, the irrigation controllers9430 a-n analyze the rainfall data obtained directly from one or more ofthe weather station servers 9470 a-n as described above, for example, inreference to the irrigation controller 8930 of FIG. 92. Based on thisanalysis of the weather data obtained from the weather station servers9470 a-n, the irrigation controllers 9430 a-n determine, as describedabove in reference to the irrigation controller 8930 of FIG. 92, tointerrupt one of more of their respective watering schedules executedvia the activation lines 9432 a-n and valves 9495 a-n after a detectedactive rainfall in the respective locations where the irrigationcontrollers 9430 a-n are installed and/or to interrupt the one or moreof the watering schedules for a predetermined interval (e.g., 24 hours,48 hours, 72 hours, etc.) of time after a detected stop of rainfall inthe respective locations where the irrigation controllers 9430 a-n,activation lines 9432 a-n, and valves 9495 a-n are installed.

Some embodiments provide interface units that interface with anirrigation controller. These interface units comprise a housing; acontroller within the housing, where the controller is adapted in partto interrupt an execution of one or more watering schedules implementedat an irrigation controller; a relay device coupled with the controllerand the irrigation controller, where the relay device is adapted tocause an interruption of an execution of a watering schedule by theirrigation controller in response to signaling from the controller; anda user interface comprising: a plurality of user input devices coupledto the controller and adapted to provide signaling to the controllerbased upon a user's engagement therewith, the plurality of user inputdevices adapted to allow the user to define parameters used by thecontroller in determining whether to interrupt irrigation; and a userdisplay coupled to the controller and adapted to display one or morepictorial representations, the user display comprising a display screen;wherein the controller is adapted to cause the user display tosimultaneously display a plurality of pictorial representations that incombination convey to a user a mode of operation and whether irrigationis being interrupted.

Some implementations provide an interface unit that interfaces with anirrigation controller. The interface unit comprise: a housing; acontroller within the housing, where the controller is adapted in partto interrupt an execution of one or more watering schedules implementedat an irrigation controller; a relay device coupled with the controllerand the irrigation controller, where the relay device is adapted tocause an interruption of an execution of a watering schedule by theirrigation controller in response to signaling from the controller; anda user interface comprising: a plurality of user input devices coupledto the controller and adapted to provide signaling to the controllerbased upon a user's engagement therewith, the plurality of user inputdevices adapted to allow the user to define parameters used by thecontroller in determining whether to interrupt irrigation; and a userdisplay coupled to the controller and adapted to display one or morepictorial representations, the user display comprising a display screen;wherein the controller is adapted to cause the user display tosimultaneously display a plurality of pictorial representations, wherethe plurality of pictorial representations in combination convey to auser that irrigation is being interrupted and one or more reasons whyirrigation is interrupted. In some instances the controller in beingadapted to cause the user display to display the plurality of pictorialrepresentations is adapted to cause the display to simultaneouslydisplay an interrupt indicator and to not display a water sprayindicator, where the combination of the interrupt indicator and the lackof display of the water spray indicator convey to a user that theirrigation is interrupted.

Similarly, some embodiments provide an interface unit that interfaceswith an irrigation controller. These embodiments comprise: a housing; acontroller within the housing, where the controller is adapted in partto interrupt an execution of one or more watering schedules implementedat an irrigation controller; a relay device coupled with the controllerand the irrigation controller, where the relay device is adapted tocause an interruption of an execution of a watering schedule by theirrigation controller in response to signaling from the controller; anda user interface comprising: a plurality of user input devices coupledto the controller and adapted to provide signaling to the controllerbased upon a user's engagement therewith, the plurality of user inputdevices adapted to allow the user to define parameters used by thecontroller in determining whether to interrupt irrigation; and a userdisplay coupled to the controller and adapted to display one or morepictorial representations, the user display comprising a display screen;wherein the controller is adapted to cause the user display tosimultaneously display a plurality of pictorial representations, wherethe plurality of pictorial representations in combination convey to auser that irrigation is being interrupted based on a user override.

Further, some embodiments provide interface units that interfaces withan irrigation controller, and comprise: a housing; a controller withinthe housing, where the controller is adapted in part to interrupt anexecution of one or more watering schedules implemented at an irrigationcontroller; a relay device coupled with the controller and theirrigation controller, where the relay device is adapted to cause aninterruption of an execution of a watering schedule by the irrigationcontroller in response to signaling from the controller; and a userinterface comprising: a plurality of user input devices coupled to thecontroller and adapted to provide signaling to the controller based upona user's engagement therewith, the plurality of user input devicesadapted to allow the user to define parameters used by the controller indetermining whether to interrupt irrigation; and a user display coupledto the controller and adapted to display one or more pictorialrepresentations, the user display comprising a display screen; whereinthe controller is adapted to cause the user display to simultaneouslydisplay a plurality of pictorial representations, where the plurality ofpictorial representations in combination convey to a user that aninterruption of irrigation is prevented based on a user override.

Additionally, some embodiments provide methods of controllingirrigation. These methods comprise: receiving from a remote sensor unitenvironmental information; determining, locally based on the receivedenvironmental information, whether to interrupt irrigation intended tobe implemented by a separate irrigation controller implementingirrigation according to an irrigation schedule; and simultaneouslydisplaying on a local display multiple pictorial representations, wherethe combination of the multiple pictorial representations conveys to auser a mode of operation and whether irrigation is being interrupted. Insome instances, these methods may further interrupt irrigation;determine rainfall, determine whether to interrupt based on rainfall anddisplay pictorial representations identifying that the interruptionbased on rainfall; determine temperature information, determine whetherto interrupt based on the temperature information, and display pictorialrepresentations identifying that the interruption is based on thetemperature information; and/or determine whether to overrideinterrupting irrigation and/or overriding irrigation and inducinginterruptions.

Further embodiments provide methods of controlling irrigation. Some ofthese methods comprise: receiving from a remote sensor unitenvironmental information; determining, locally based on the receivedenvironmental information, whether to interrupt irrigation intended tobe implemented by a separate and distinct irrigation controllerimplementing irrigation according to an irrigation schedule; andsimultaneously displaying on a local display multiple pictorialrepresentations, where the combination of the multiple pictorialrepresentations conveys to a user that irrigation is being interruptedand one or more reasons why irrigation is interrupted in response todetermining to interrupt irrigation.

Some embodiments provide methods of providing notifications of operatingstatus in controlling irrigation. These methods comprise: determining acurrent state of operation in allowing or interrupting irrigation asimplemented by a separate and remote irrigation controller implementingthe irrigation in accordance with an irrigation schedule; andsimultaneously displaying, on a local display that is not part of and isseparate from the irrigation controller, multiple pictorialrepresentations based on the determined current state of operation,where the combination of the multiple pictorial representations conveysto a user the current state of operation and whether irrigation isinterrupted.

In some embodiments, a method is provided for use in controllingirrigation. These methods comprise: receiving a user defined rainfallparameter; receiving, from a remote sensor, rainfall information; anddisplaying, in response to the rainfall information, a plurality ofpictorial representations corresponding to the rainfall information anda state of interrupting irrigation based on a relationship between therainfall information and the user defined rainfall parameter.

Additionally or alternatively, some embodiments provide methods ofcontrolling irrigation. Some of these methods comprise: receiving a userdefined temperature parameter; receiving, from a remote sensor,temperature information; and displaying, in response to the temperatureinformation, a plurality of pictorial representations corresponding tothe temperature information and a state of interrupting irrigation basedon a relationship between the temperature information and the userdefined temperature parameter.

Some embodiments comprise a processor; and a memory that storesexecutable program code, wherein the processor is configured to executethe executable program code to: receive from a remote sensor unitenvironmental information; determine, locally based on the receivedenvironmental information, whether to interrupt irrigation intended tobe implemented by a separate irrigation controller implementingirrigation according to an irrigation schedule; and simultaneouslydisplay on a local display multiple pictorial representations, where thecombination of the multiple pictorial representations conveys to a usera mode of operation and whether irrigation is being interrupted. In someinstances, these methods may further interrupt irrigation; determinerainfall, determine whether to interrupt based on rainfall and displaypictorial representations identifying that the interruption based onrainfall; determine temperature information, determine whether tointerrupt based on the temperature information, and display pictorialrepresentations identifying that the interruption is based on thetemperature information; and/or determine whether to overrideinterrupting irrigation and/or overriding irrigation and inducinginterruptions.

Similarly, some embodiments comprise a processor; and a memory thatstores executable program code, wherein the processor is configured toexecute the executable program code to: receive from a remote sensorunit environmental information; determine, locally based on the receivedenvironmental information, whether to interrupt irrigation intended tobe implemented by a separate and distinct irrigation controllerimplementing irrigation according to an irrigation schedule; andsimultaneously display on a local display multiple pictorialrepresentations, where the combination of the multiple pictorialrepresentations conveys to a user that irrigation is being interruptedand one or more reasons why irrigation is interrupted in response todetermining to interrupt irrigation.

Some embodiments comprise a processor; and a memory that storesexecutable program code, wherein the processor is configured to executethe executable program code to: determine a current state of operationin allowing or interrupting irrigation as implemented by a separate andremote irrigation controller implementing the irrigation in accordancewith an irrigation schedule; and simultaneously display, on a localdisplay that is not part of and is separate from the irrigationcontroller, multiple pictorial representations based on the determinedcurrent state of operation, where the combination of the multiplepictorial representations conveys to a user the current state ofoperation and whether irrigation is interrupted.

Further embodiments comprise a processor; and a memory that storesexecutable program code, wherein the processor is configured to executethe executable program code to: receive a user defined rainfallparameter; receive, from a remote sensor, rainfall information; anddisplay, in response to the rainfall information, a plurality ofpictorial representations corresponding to the rainfall information anda state of interrupting irrigation based on a relationship between therainfall information and the user defined rainfall parameter.

Additionally, some embodiments comprise a processor; and a memory thatstores executable program code, wherein the processor is configured toexecute the executable program code to: receive a user definedtemperature parameter; receive, from a remote sensor, temperatureinformation; and display, in response to the temperature information, aplurality of pictorial representations corresponding to the temperatureinformation and a state of interrupting irrigation based on arelationship between the temperature information and the user definedtemperature parameter. Several embodiments provide an interface unitinterfacing with an irrigation controller, where the interface unitcomprises: a housing; a controller within the housing, where thecontroller is adapted in part to interrupt an execution of one or morewatering schedules implemented at an irrigation controller; a relaydevice coupled with the controller and the irrigation controller, wherethe relay device is adapted to cause an interruption of an execution ofa watering schedule by the irrigation controller in response tosignaling from the controller; and a user interface comprising: aplurality of user input devices coupled to the controller and adapted toprovide signaling to the controller based upon a user's engagementtherewith, the plurality of user input devices adapted to allow the userto define parameters used by the controller in determining whether tointerrupt irrigation; and a user display coupled to the controller andadapted to display one or more pictorial representations, the userdisplay comprising a display screen; wherein the controller is adaptedto cause the user display to simultaneously display a plurality ofpictorial representations that in combination convey to a user a mode ofoperation and whether irrigation is being interrupted.

In some embodiments, the invention can be characterized as a method ofcontrolling irrigation, comprising: receiving a user defined rainfallthreshold; receiving, from a remote sensor, rainfall information; anddisplaying, in response to the rainfall information, multiple pictorialrepresentations corresponding to the rainfall information and a state ofinterrupting irrigation based on a relationship between the rainfallinformation and the user defined rainfall threshold.

In another embodiment, the invention can be characterized as anirrigation controller comprising: a housing; a controller within thehousing, where the controller is adapted to implement irrigationaccording to one or more watering schedules and further adapted tointerrupt irrigation; activation lines each coupled to a valve toactivate the one or more valves as instructed by the controller inaccordance with the one more irrigation schedules implemented by thecontroller; and a user interface comprising: a plurality of user inputdevices coupled to the controller and adapted to provide signaling tothe controller based upon a user's engagement therewith, the pluralityof user input devices adapted to allow the user to define parametersused by the controller in determining whether to interrupt irrigation;and a user display coupled to the controller and adapted to display oneor more pictorial representations, the user display comprising a displayscreen; wherein the controller is adapted to cause the user display tosimultaneously display a plurality of pictorial representations, wherethe plurality of pictorial representations in combination convey to auser that irrigation is being interrupted and one or more reasons whyirrigation is interrupted.

Some embodiments provide an interface unit comprising: a housing; acontroller within the housing configured to interrupt execution of awatering schedule implemented at an irrigation controller; a relaydevice configured to cause an interruption of a watering schedule inresponse to signaling from the controller; and a user interfacecomprising: a plurality of user input devices configured to providesignaling to the controller based upon a user's engagement therewith,and configured to allow the user to define parameters used by thecontroller in determining whether to interrupt irrigation; and a userdisplay configured to display one or more pictorial representations, theuser display comprising a display screen; the controller is configuredto cause the user display to simultaneously display a plurality ofpictorial representations that in combination convey to a user a mode ofoperation and whether irrigation is being interrupted.

Further, some embodiments provide irrigation controllers that comprise:a housing; a controller within the housing, where the controller isconfigured to implement irrigation according to one or more wateringschedules and further configured to cause an interruption of theirrigation; activation lines each coupled to a valve to activate the oneor more valves as instructed by the controller in accordance with theone more irrigation schedules implemented by the controller; and a userinterface comprising: a plurality of user input devices coupled to thecontroller and configured to provide signaling to the controller basedupon a user's engagement therewith, the plurality of user input devicesconfigured to allow the user to define at least the user enteredtemperature threshold parameter and the user entered rainfall thresholdparameter; and a user display comprising a display screen and coupled tothe controller and configured to display one or more pictorialrepresentations; wherein the controller is configured to cause thedisplay screen to display a plurality of pictorial representations,where the plurality of pictorial representations in combination conveyto the user that the irrigation is being interrupted and one or morereasons why irrigation is interrupted.

Furthermore, at least some of these irrigation controllers can furthercomprise: a receiver coupled with the controller, wherein the receiveris configured to receive a communication from a remote sensor, where thecommunication comprises sensed rainfall information; and the controlleris configured to: receive the sensed rainfall information and determine,at the controller and based on the sensed rainfall information, whethera rainfall threshold has been exceeded; and cause the interruption ofthe irrigation schedule when the rainfall threshold has been exceeded;and wherein the controller in being configured to cause the displayscreen to display the plurality of pictorial representations isconfigured to cause the display screen to display, in response todetermining that the rainfall threshold has been exceeded, an interruptindicator and a rain indicator, wherein the combination of the interruptindicator and the rain indicator conveys to a user that the irrigationis interrupted based on the sensed rainfall information. Additionally,in some implementations the communication from the remote sensorcomprises sensed temperature information; and the controller isconfigured to: receive the sensed temperature information and determine,at the controller, whether a sensed temperature is below a temperaturethreshold; and cause the interruption of the irrigation schedule whenthe sensed temperature is below the temperature threshold; wherein thecontroller in being configured to cause the display screen to displaythe plurality of pictorial representations is configured to cause thedisplay screen to display a temperature indicator in response todetermining that the sensed temperature is below the temperaturethreshold, wherein a combination of the interrupt indicator, the rainindicator and the temperature indicator conveys to the user that theirrigation is interrupted based on the sensed rainfall information andthe sensed temperature information.

Reference throughout this specification to “one embodiment,” “anembodiment,” “some embodiments,” or similar language means that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment of thepresent invention. Thus, appearances of the phrases “in one embodiment,”“in an embodiment,” “in some embodiments” and similar languagethroughout this specification may, but do not necessarily, all refer tothe same embodiment.

While the invention herein disclosed has been described by means ofspecific embodiments, examples and applications thereof, numerousmodifications and variations could be made thereto by those skilled inthe art without departing from the scope of the invention set forth inthe claims.

What is claimed is:
 1. A system for controlling irrigation based onrainfall, the system comprising: an irrigation controller configured toexecute one or more watering schedules and including a wirelesstransceiver; a server remote to a location where the irrigationcontroller is installed, the server being in communication with theirrigation controller over a network, the network comprising a wirelesslocal area network, wherein the wireless transceiver of the irrigationcontroller is communicationally coupled to the wireless local areanetwork; wherein the server includes a control unit configured to:transmit a first signal to the irrigation controller, via the wirelesslocal area network and the wireless transceiver, to cause aninterruption of one or more watering schedules executed by theirrigation controller in response to weather data indicative of activerainfall, in the location where the irrigation controller is installed,reaching an interrupt threshold that is associated with a presetrainfall accumulation amount; and transmit a second signal to theirrigation controller, via the wireless local area network and thewireless transceiver, to cause a removal of the interruption of the oneor more watering schedules executed by the irrigation controller after acompletion of a predetermined interval of time and without determiningwhether the rainfall accumulation amount is above the interruptthreshold or below the interrupt threshold in response to weather dataindicative of a rainfall stop in the location where the irrigationcontroller is installed.
 2. The system of claim 1, wherein thepredetermined interval of time of the interruption is one ofpre-programmed into the control unit and preset by a user.
 3. The systemof claim 1, wherein the predetermined interval of time of theinterruption is at least 48 hours.
 4. The system of claim 1, wherein thecontrol unit is configured to, in response to the weather dataindicative of the rainfall stop, initiate a timer configured to countdown a remainder of time left on the predetermined interval of time ofthe interruption.
 5. The system of claim 4, wherein the control unit isconfigured to obtain weather data associated with the location where theirrigation controller is installed at intermittent intervals during acountdown, by the timer, of the remainder of time left on thepredetermined interval of time of the interruption.
 6. The system ofclaim 5, wherein the control unit is configured to, at one of theintermittent intervals, permit the timer to continue the countdown ofthe remainder of time left on the interval of time of the interruptionin response to a determination, by the control unit, that the weatherdata obtained at the one of the predetermined intervals indicates norainfall.
 7. The system of claim 5, wherein the control unit isconfigured to, at one of the intermittent intervals, reset the timer torestart a countdown of the remainder of time left on the predeterminedinterval of time of the interruption in response to a determination, bythe control unit, that the weather data obtained at the one of theintermittent intervals indicates active rainfall.
 8. The system of claim1, further comprising at least one weather data server remote to theserver and configured to transmit weather data associated with thelocation where the irrigation controller is installed to the server overthe network.
 9. The system of claim 8, further comprising a databaseconfigured to store the weather data associated with the location wherethe irrigation controller is installed, the database being configured toreceive the weather data associated with the location where theirrigation controller is installed from one of the at least one weatherdata server and the server.
 10. The system of claim 1, wherein theirrigation controller further comprises a housing and a user interfaceintegrated with the housing and comprising a plurality of user inputdevices coupled to the control unit and a user display coupled to thecontrol unit.
 11. A method for controlling irrigation based on rainfall,the method comprising: providing an irrigation controller configured toexecute one or more watering schedules and including a wirelesstransceiver; providing a server remote to a location where theirrigation controller is installed, the server being in communicationwith the irrigation controller over a network, the network comprising awireless local area network, wherein the wireless transceiver of theirrigation controller is communicationally coupled to the wireless localarea network, the server including a control unit; transmitting a firstsignal to the irrigation controller, via the wireless local area networkand the wireless transceiver, to cause, via the control unit, aninterruption of one or more watering schedules executed by theirrigation controller in response to weather data indicative of activerainfall, in the location where the irrigation controller is installed,reaching an interrupt threshold that is associated with a presetrainfall accumulation amount; and transmit a second signal to theirrigation controller, via the wireless local area network and thewireless transceiver, to cause, via the control unit, a removal of theinterruption of the one or more watering schedules executed by theirrigation controller after a completion of a predetermined interval oftime and without determining whether the rainfall accumulation amount isabove the interrupt threshold or below the interrupt threshold inresponse to weather data indicative of a rainfall stop in the locationwhere the irrigation controller is installed.
 12. The method of claim11, wherein the predetermined interval of time of the interruption isone of pre-programmed into the control unit and preset by a user. 13.The method of claim 11, wherein the predetermined interval of time ofthe interruption is at least 48 hours.
 14. The method of claim 11,further comprising, in response to the receipt of the weather dataindicative of the rainfall stop, initiating a timer configured to countdown a remainder of time left on the predetermined interval of time ofthe interruption.
 15. The method of claim 11, further comprisingproviding: at least one weather data server remote to the server andconfigured to transmit weather data associated with the location wherethe irrigation controller is installed to the server over the network;and providing a database configured to store the weather data associatedwith the location where the irrigation controller is installed, thedatabase being configured to receive the weather data associated withthe location where the irrigation controller is installed from one ofthe at least one weather data server and the server.
 16. A system forcontrolling irrigation based on rainfall, the system comprising: anirrigation controller configured to execute one or more wateringschedules and including a wireless transceiver; a weather station sourcein communication with the irrigation controller over a networkcomprising a wireless local area network, wherein the wirelesstransceiver of the irrigation controller is communicationally coupled tothe wireless local area network; wherein the irrigation controller isconfigured to obtain, from the weather station source and over thenetwork via the wireless local area network and the wirelesstransceiver, weather data associated with a location where theirrigation controller is installed; and wherein the irrigationcontroller includes a control unit configured to: cause an interruptionof one or more watering schedules executed by the irrigation controllerin response to receipt of weather data indicative of active rainfall, inthe location where the irrigation controller is installed, reaching aninterrupt threshold that is associated with a preset rainfallaccumulation amount; and remove the interruption of the one or morewatering schedules executed by the irrigation controller after acompletion of a predetermined interval of time and without determiningwhether the rainfall accumulation amount is above the interruptthreshold or below the interrupt threshold in response to receipt ofweather data indicative of a rainfall stop in the location where theirrigation controller is installed.
 17. The system of claim 16, whereinthe predetermined interval of time of the interruption is one ofpre-programmed into the control unit and preset by a user.
 18. Thesystem of claim 16, wherein the predetermined interval of time of theinterruption is at least 48 hours.
 19. The system of claim 16, whereinthe control unit is configured to, in response to the receipt of theweather data indicative of the rainfall stop, initiate a timerconfigured to count down a remainder of time left on the predeterminedinterval of time of the interruption.
 20. The system of claim 19,wherein the control unit is configured to obtain the weather data atintermittent intervals during a countdown, by the timer, of theremainder of time left on the predetermined interval of time of theinterruption.
 21. The system of claim 20, wherein the control unit isconfigured to, at one of the intermittent intervals, permit the timer tocontinue the countdown of the remainder of time left on the interval oftime of the interruption in response to a determination, by the controlunit, that weather data received at the one of the predeterminedintervals indicates no active rainfall.
 22. The system of claim 20,wherein the control unit is configured to, at one of the intermittentintervals, reset the timer to restart a countdown of the remainder oftime left on the predetermined interval of time of the interruption inresponse to a determination, by the control unit, that the weather datareceived at the one of the intermittent intervals indicates activerainfall.
 23. The system of claim 16, wherein the weather station sourcecomprises at least one weather data server remote to the location wherethe irrigation controller is installed and configured to transmit theweather data to the irrigation controller over the network.
 24. Thesystem of claim 23, further comprising a database configured to storethe weather data associated with the location where the irrigationcontroller is installed, the database being configured to receive theweather data associated with the location where the irrigationcontroller is installed over the network from the weather stationsource.
 25. The system of claim 16, wherein the weather station sourceis a weather station server.
 26. The system of claim 25, wherein theweather station server is remote to the location where the irrigationcontroller is installed.
 27. A method for controlling irrigation basedon rainfall, the method comprising: providing an irrigation controllerconfigured to execute one or more watering schedules and including awireless transceiver; providing a weather station source incommunication with the irrigation controller over a network comprising awireless local area network, wherein the wireless transceiver of theirrigation controller is communicationally coupled to the wireless localarea network; obtaining, via the irrigation controller, from the weatherstation source and over the network via the wireless local area networkand the wireless transceiver, weather data associated with a locationwhere the irrigation controller is installed; causing, via a controlunit of the irrigation controller, an interruption of one or morewatering schedules executed by the irrigation controller in response toreceipt of weather data indicative of active rainfall, in the locationwhere the irrigation controller is installed, reaching an interruptthreshold that is associated with a preset rainfall accumulation amount;and removing, via the control unit of the irrigation controller, theinterruption of the one or more watering schedules executed by theirrigation controller after a completion of a predetermined interval oftime and without determining whether the rainfall accumulation amount isabove the interrupt threshold or below the interrupt threshold inresponse to receipt of weather data indicative of a rainfall stop in thelocation where the irrigation controller is installed.
 28. The method ofclaim 27, wherein the predetermined interval of time of the interruptionis one of pre-programmed into the control unit and preset by a user. 29.The method of claim 27, wherein the predetermined interval of time ofthe interruption is at least 48 hours.
 30. The method of claim 27,further comprising, in response to the receipt of the weather dataindicative of the rainfall stop, initiating by the irrigation controllera timer configured to count down a remainder of time left on thepredetermined interval of time of the interruption.
 31. The method ofclaim 27, wherein the weather station source comprises at least oneweather data server remote to the location where the irrigationcontroller is installed and configured to transmit the weather data tothe irrigation controller over the network.
 32. The method of claim 31,further comprising providing a database configured to store the weatherdata associated with the location where the irrigation controller isinstalled, the database being configured to receive the weather dataassociated with the location where the irrigation controller isinstalled over the network from the weather station source.
 33. Themethod of claim 27, wherein the weather station source is a weatherstation server.
 34. The method of claim 33, wherein the weather stationserver is remote to the location where the irrigation controller isinstalled.